AGENTS.md: the feature-request loop

When an agent is asked for a feature it runs the whole loop itself: check open
PRs for the area first, work in a new worktree on the latest upstream main,
build and run pr_ready, then push to the fork and open the pull request
against upstream, never the fork.

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This commit is contained in:
socksprox
2026-10-25 21:54:47 +01:00
parent 731d88a1d8
commit 8dcd00fc62
+4
View File
@@ -27,6 +27,10 @@ Feature → files → harness for the most-changed areas: [docs/architecture.md]
change), none for a fix. Agents never add `release-now`: the maintainer decides it. Merges ship in batches of 5, or after
6 hours ([docs/release-flow.md](docs/release-flow.md)).
- Contributors first: `gh pr list --state open --search <area>` before you start; never duplicate theirs.
- Asked for a feature? Run the whole loop: check open PRs for the area (above), work in a new worktree,
`git fetch` the upstream remote (`ludovic111/horizon`) and start from its latest `main`, build, run
`tools/pr_ready.py`, then push to your fork and open the pull request against upstream's `main` —
never against the fork itself.
## Crates