What problem does it solve? Architecture decision records (ADRs) often get approved without independent scrutiny, letting vague decisions, missing trade-offs, or silent contradictions with earlier ADRs slip into the permanent project log. This Skill provides an independent, clean-context review of an ADR so the document must stand on its own before it becomes a long-lived reference. ## Core Features & Use Cases - Formal conformance check: Validates file naming, numbering, status values, and template structure against the project's ADR conventions, treating the existing log as the authoritative style baseline. - Content quality review: Assesses whether the decision is concrete, alternatives are real, consequences admit costs, open questions are honest, and no conflict with other accepted ADRs goes undisclosed. - Accepted-ADR diff guard: For changes to already-accepted ADRs, verifies line-by-line that only permitted sections changed, catching unauthorized rewrites of accepted decisions. - PR integration: Posts the review report as a pull request comment on GitHub or Gitea when a PR exists. - Use Case: After drafting ADR-0007 proposing a new caching layer, run this Skill to receive a verdict (Approved or Returned for rework) with findings ranked by severity before merging. ## Quick Start Ask the assistant to review ADR 7 in the project and confirm whether the decision is ready to be accepted.
