code-reviewer

Review PR diffs against formal spec artifacts for requirement coverage.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/tjespers/claude-skills --skill code-reviewer-tjespers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/tjespers/claude-skills/tree/main/code-reviewer
Command: npx skills add https://github.com/tjespers/claude-skills --skill code-reviewer-tjespers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews can miss gaps between specifications and implementations, leading to defects and misaligned features. This skill provides a structured check against the code changes in a PR to ensure alignment with the spec.

Core Features & Use Cases

  • FR coverage verification against spec artifacts (FR MUST/MUST/SHOULD)
  • Design decision compliance verification against plan.md
  • Architecture layer discipline validation (domain vs application vs infrastructure boundaries)
  • Entity/DTO alignment checks with data-model outlines
  • Phantom feature detection and deferral awareness
  • Constitution and commit-scope checks

Quick Start

Provide a PR number or branch name to start a compliance review against the repository spec and PR changes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I verify PR compliance against a specification document?

PR compliance verification identifies gaps between implementation changes and specification artifacts by reviewing diffs to ensure FR coverage, design decision adherence, and architecture discipline. It checks MUST requirements are fully implemented and SHOULD items are appropriately handled.

What is functional requirement coverage analysis in code review?

Functional requirement coverage analysis evaluates PR diffs against formal spec artifacts like spec.md to confirm MUST FRs are fully implemented and SHOULD or DEFERRED items are managed correctly according to project constraints.

Can I check architecture layer discipline and entity alignment in a PR review?

Yes, PR review can validate architecture layer discipline by checking domain versus application versus infrastructure boundaries and verifying entity and DTO alignment with data-model outlines outlined in formal plan documents.

How do I detect phantom features and deferral gaps during a spec audit?

Spec audits detect phantom features by cross-referencing PR diffs against specification artifacts, flagging unrequested additions and ensuring deferred items are handled according to plan constraints and constitution gates.

Do I need formal spec artifacts to run an automated spec compliance audit?

Yes, automated spec compliance audits require formal spec artifacts like spec.md and plan.md in the codebase to evaluate PR diffs against functional requirements, design decisions, and architecture boundaries effectively.

What are the limitations of automated PR review for spec compliance?

Automated spec compliance PR review is limited to codebases with formal spec artifacts and focuses on FR coverage, design decisions, architecture discipline, and entity alignment, without evaluating runtime behavior or performance metrics.