Reviewing a repository against its standards

This skill is guidance, not a complete checklist. Verify the PR's live base and head, then read the diff and enough surrounding context to understand the design before judging. A short review with one substantiated blocker beats a list of nits.

For code-facing reviews — lifecycle, concurrency, invariants, disposal, and other implementation semantics — also load the code review checklist.

Sources of truth

• The repository's root AGENTS.md: skill authoring, validation, and quality-gate rules.
• The repository's documentation standard (usually docs/AGENTS.md): placement and prose discipline.
• prose-standard: required coverage and editorial judgment.
• trim-cot-leakage and prune-prompt-pollution: reasoning-transcript and prompt-pollution smells respectively.
• The repository's Agent Note rules (usually .agents/notes/README.md): format and scope. Treat disagreement with a note as a design discussion, not an automatic veto.
• The repository's bilingual pairing contract and terminology table (usually docs/i18n/README.md and docs/i18n/terminology.md).

Blocking requirements