Skip to content

docs: shared agent and Bugbot guardrails #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bschellenberger2600 wants to merge 1 commit into from
Closed

docs: shared agent and Bugbot guardrails #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .cursor/BUGBOT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# Bugbot review guidance

## Global expectations

- **Latest head:** Assume the PR branch reflects the latest pushed commits; if review context looks stale relative to GitHub, refresh before commenting.
- **No force-push:** Do not suggest force-pushing shared branches as the default fix.
- **Prioritize behavior:** Flag correctness, security, compatibility, and API or contract risks ahead of style-only feedback unless style obscures a defect.
- **Trust CI:** When CI already enforces formatting or static analysis, avoid duplicating that noise in comments unless the check is wrong or misleading.


15 changes: 15 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,20 @@
# AGENTS.md

## Agentic guardrails

These apply to human and automated contributors (including Cloud Agents).

1. **Work from the latest branch tip**
Before you start work on a branch: `git fetch origin`, check it out, then `git merge --ff-only origin/<branch>` (or `git pull --ff-only` when upstream is configured). If you cannot fast-forward, stop and align with the repository's normal merge or rebase workflow. Do not silently work on a stale checkout.

2. **Never force-push shared history**
Do not `git push --force`, `git push --force-with-lease`, or rewrite published branch history unless a maintainer explicitly authorizes that operation for the exact repository and branch.

3. **Focused changes and verification**
Keep pull requests scoped; run this repository's standard build, test, and lint commands (see README, Makefile, or CLAUDE.md) before requesting review.

---

## Cursor Cloud specific instructions

This is a **pure Go test-utility library** with zero external dependencies beyond the Go toolchain and `git` CLI. There are no services, databases, or containers to start.
Expand Down
Loading