Skip to content

docs: add review-proven failure-path & async-state rules to AGENTS.md - #7061

Open
jedwards27 wants to merge 1 commit into
mainfrom
judeedwards/review-proven-rules
Open

docs: add review-proven failure-path & async-state rules to AGENTS.md#7061
jedwards27 wants to merge 1 commit into
mainfrom
judeedwards/review-proven-rules

Conversation

@jedwards27

Copy link
Copy Markdown
Contributor

Mining the last 25 PRs' review threads (45 substantive findings, 11 reviewed PRs, avg 4.8 review rounds each) shows 53% of findings are repeats of five clusters: swallowed failures, stale-async-state races, tests that don't bind the production seam, unbounded resources/retry loops, and non-atomic multi-step persistence. PR #6956 alone burned 4 rounds converging on one of these classes.

This PR distills those clusters into six imperative rules in AGENTS.md so agents apply them before writing code, adds one client-consumption invariant to ARCHITECTURE.md §5, and places the test-quality rule in TESTING.md (per the team decision that testing docs are the canonical guide for review standards), cross-referenced from AGENTS.md. Each rule cites the PRs where it was litigated. Raw mining data: reviews.jsonl / comments.jsonl (review-mining artifacts, not committed).

No code changes. CLAUDE.md is a symlink to AGENTS.md and picks this up automatically.

🤖 Drafted by Jude's agent from automated mining of this repo's last 25 PRs' review threads; every rule cites the PRs where it was litigated. Jude reviews and owns the result. Mining method + raw cluster data available on request.

Distills recurring review findings from the last 25 PRs into six imperative rules in AGENTS.md, plus one client-consumption invariant in ARCHITECTURE.md §5. Docs only.

Signed-off-by: Jude Edwards <judeedwards@squareup.com>
@jedwards27
jedwards27 requested a review from a team as a code owner August 30, 2026 17:26
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is eed74bde2f4797714335ac10c56c0b0244c1def4...0ecf111f46275509ade52a293c5968bbb6dce1a1.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review 0ecf111f46275509ade52a293c5968bbb6dce1a1 to authorize a new review.
Any previous review applies only to its recorded range.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant