review

Validate PRs and branches against existing ADRs and detect new architectural decisions.

4|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rvdbreemen/adr-kit --skill review-rvdbreemen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rvdbreemen/adr-kit/tree/main/skills/review
Command: npx skills add https://github.com/rvdbreemen/adr-kit --skill review-rvdbreemen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit reviews Pull Requests (PRs) or branches for adherence to architectural decision records (ADRs) and identifies any new architectural decisions introduced.

Core Features & Use Cases

  • PR/branch ADR Audit: Validates committed work against project ADRs.
  • Enforcement: Checks if any changes violate existing ADRs.
  • Discovery: Identifies new decisions that are not documented in ADRs yet.
  • Use Case: Before merging a PR, use this skill to ensure compliance and catch any overlooked architectural decisions.

Quick Start

Run the 'adr-kit review' command on a PR or branch to audit the architectural decisions.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a pull request violates existing architecture decisions?

To check if a pull request violates architecture decisions, you can audit the PR against your project's ADRs. This skill validates committed code changes to ensure compliance with documented architectural decision records before merging.

Can I discover undocumented architectural decisions in a branch before merging?

Yes, you can discover undocumented architectural decisions in a branch by running an ADR audit. The review process compares code changes against existing records to identify new architectural decisions that have not yet been documented.

What is an ADR compliance audit for software development workflows?

An ADR compliance audit is a review process that validates code changes against architectural decision records. It enforces adherence to established decisions and discovers new architectural choices introduced in pull requests or branches.

How do I audit a branch for architectural decision records using adr-kit?

To audit a branch for architectural decision records, run the 'adr-kit review' command. This validates the branch work against existing ADRs to ensure compliance and detects any newly introduced architectural decisions.

Do I need existing ADRs to review a pull request for architectural decisions?

You need existing ADRs to validate compliance, but the review process also handles decision discovery. It compares code changes to current records to enforce rules and identifies new architectural decisions even if no prior ADRs exist.

What are the limitations of automated ADR compliance checks on PRs?

Automated ADR compliance checks on PRs are limited by the scope of existing architectural decision records and the code changes analyzed. They validate against documented decisions and discover new ones, but require defined ADRs for enforcement.