Repo rules for agents

Shared by Codex and Claude Code. Every line here should change what you do.
## 1. Plan before you touch code
- Long task: first tell me in 2-3 sentences what you think I'm after
- Start only after I say yes

Complete the current task with the minimum sufficient change.
## Before editing
- Read the relevant code, tests, and configuration directly. Do not work from search snippets or guesses.
- If the requirement is ambiguous or the premise is unverified, resolve that before building on it.

- think before coding: ask when unsure, don't silently pick one interpretation and run with it
- simplicity first: minimum code, any overengineering shows at a glance
- surgical edits: only touch what's required, don't fix up neighboring code on the way by
- goal-driven: translate fuzzy instructions into verifiable targets before starting

Writing rules, from Orwell, 1946. These govern prose: docs, PR text, messages. Never touch code or technical terms; swap in everyday words only where precision survives.
1. Never use a metaphor, simile or other figure of speech which you are used to seeing in print.
2. Never use a long word where a short one will do.
3. If it is possible to cut a word out, always cut it out.

Use gh to scan the 50 most recent PRs in each GitHub repo under [CODE DIRECTORY]. Find the issues [REVIEWER GITHUB USERNAME] keeps flagging. Rank them by frequency and link the relevant PRs. Wait for my approval, then add only the rules I choose to ~/.codex/AGENTS.md.