generate-code-review-rules

# Generate Code Review Rules Create concise rules that help reviewers distinguish real defects from noise. Read [rules-template.md](references/rules-template.md) before editing. ## Workflow 1. Locate the repository root and all existing `AGENTS.md` files. Read the applicable instruction hierarchy before editing. 2. Inspect evidence without changing state: - build, test, lint, type-check, and formatting configuration; - CI workflows and required checks; - package/module manifests and supported runtimes/platforms; - public API, schema, migration, compatibility, generated-code, and test conventions; - recurring review guidance already documented in the repository. 3. Convert only stable, repository-specific evidence into review rules. Every rule must name what a reviewer should verify and when it applies. Do not invent conventions from one incidental example. 4. Choose scope deliberately: - Put repository-wide rules in the root `AGENTS.md`. - Put specialized rules in a nested `AGENTS.md` only when they apply exclusively to that subtree. - Do not duplicate a parent rule in children. 5. Create or replace exactly one `## Code Review Rules` section in each selected file while preserving all unrelated content and formatting. If `AGENTS.md` does not exist, create the minimum file needed. 6. Review the resulting diff. Remove generic advice, style preferences already enforced mechanically, unverified commands, and rules that cannot produce a clear pass/fail review decision. 7. Report which files changed and cite the repository evidence behind each added rule. Do not run the PR review automatically. Keep the section compact. Prefer 3–10 strong bullets over an exhaustive checklist. Do not hard-code branch names, file layouts, tools, languages, or hosting providers unless the repository evidence establishes them.