judge

Review staged git diffs against accepted architectural decision records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of non-compliance with architectural decisions by providing an interactive way to review staged git diffs against project's Accepted ADRs, guiding the user through resolution paths.

Core Features & Use Cases

  • Compliance Check: Interactively review staged git diffs against Accepted ADRs.
  • Resolution Guidance: Offers three resolution paths: write a new ADR, supersede an existing one, or fix the code.
  • Use Case: Before committing changes, use the Skill to ensure compliance with the project's architectural decisions, reducing the risk of non-compliant code.

Quick Start

Run /adr-kit:judge to review the staged diff against project ADRs.

Frequently Asked Questions about judge

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

FAQPage Schema
How do I check staged git diffs for ADR compliance before committing?

To check staged git diffs for ADR compliance, this Skill reviews your changes against accepted Architectural Decision Records and interactively guides you through resolution paths for any violations.

What is the best way to enforce architectural decision records during code review?

The best way to enforce architectural decision records during code review is interactively checking staged diffs against accepted ADRs, offering options to fix the code or supersede the existing decision.

Can I resolve ADR compliance issues without manually rewriting code?

You can resolve ADR compliance issues interactively without immediately rewriting code by choosing to write a new ADR or supersede an existing one, though fixing the code remains an available resolution path.

How does interactive resolution work for architectural decision violations?

Interactive resolution for architectural decision violations works by evaluating staged git diffs against accepted ADRs, potentially invoking an LLM for decision evaluation, and presenting three distinct resolution paths to the developer.

Do I need accepted ADRs in my project to review staged diffs for compliance?

You need accepted Architectural Decision Records in your project repository to effectively review staged diffs, as the compliance check evaluates your staged changes directly against those established architecture decisions.

What happens when my staged code changes violate an existing architectural decision record?

When staged code changes violate an existing architectural decision record, the Skill halts the process and interactively offers resolution paths: write a new ADR, supersede the conflicting one, or fix the code.