docs: drop the forced code-review neighbour from where-it-fits

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-08-05 11:55:49 +01:00
co-authored by Claude Opus 5
parent b0bae9921e
commit 0208cbc093
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -12,4 +12,4 @@ The rewrite keeps the levers to one compact list and spends the page on the judg
- **The scope is stated as a test**, not a list: does an agent read this document and act? Skills, `AGENTS.md`, specs, tickets and runtime prompts all pass it.
- **A "Common questions" section** answers the nine highest-volume ones directly, including the rename, the "streamline" failure where an agent trims for length and cuts behaviour, whether to rewrite documents per model, the skill that only works on the one task it was built from, and the leading-word question from non-native English speakers.
- **"It's working if"** added, led by the sharpest signal: the document gets shorter as it gets better, and duplication is the most reliable sign it was never tested.
- **`Where it fits`** now names `code-review` as the neighbour — standards on code, standards on the prose an agent executes from.
- **`Where it fits`** says plainly that it has no chain neighbour: it sits underneath the set rather than beside one skill, and the documents the other skills leave behind are the text it governs.