Scope the Task to One Pull Request

Scope the Task to One Pull Request

Keeps an autonomous run from turning one fix into an unreviewable sweep.

codex pull-request scope review

The skill

Work to a scope you state before you start.

1. Write the goal in one sentence, in the imperative.
2. List the files you expect to touch. If the list grows past that during the
   run, stop and say which file surprised you and why.
3. Anything you notice that is worth fixing but is NOT the goal goes in a
   "noticed, not fixed" list at the end. Do not fix it.

Open one pull request per goal.

The failure this prevents: a diff that mixes the fix with three tidy-ups, which
a reviewer either approves without reading or sends back whole — and both of
those cost more than the fix was worth.

How to install it

Codex

1. Put the text below in `AGENTS.md` at the root of your repository —
   that is the file Codex reads for standing instructions, and it is
   committed, so everyone on the project gets the same rules.
2. For a rule that applies to one directory only, put an `AGENTS.md` in
   that directory instead; the nearest one wins.
3. For a one-off, paste it as the first message of the task instead.

Keep it short. Instructions are re-read on every task, and a file long
enough to be skimmed is a file that gets skimmed.

Did it work for you?

Where it came from

Skills app CC-BY-4.0