codify-rule

To convert a GitHub code review comment into a reusable handbook entry, provide the PR number or comment URL to generate a structured rule draft. The system requires interactive resolution of file:line context and explicit operator Y/N approval before writing the finalized entry.

The best way to enforce code review feedback is to codify missed comments into structured handbook entries with optional blocking or advisory enforcement. This captures the insight for future PR checks and routes it to the correct domain, architecture, general, or language bucket.

To capture missed review feedback and prevent it from disappearing into one-off chatter, codify the review miss into a durable, operator-curated handbook entry. The process appends a required source footer with the PR number, author, and date for full auditability.

Yes, you can route codified review rules into specific domain, architecture, general, and language handbook buckets. The system deterministically writes to the correct handbook path using the proper frontmatter conventions required for domain rules.

To add source attribution to a newly created development handbook rule, the system automatically appends a required source footer during the writing process. This footer includes the original PR number, author, and date to ensure traceable provenance for auditability.

Yes, codifying a code review rule requires explicit manual operator approval before any file is written. You must provide a yes, edit, or no response during the interactive resolution step to authorize writing the structured handbook entry.