code-review

Validate pull requests against SDD artifacts and CLAUDE.md rules.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill code-review-juan-estrada-itti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/juan-estrada-itti/way-of-work-tools/tree/main/skills/code-review
Command: npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill code-review-juan-estrada-itti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PR-diff, CLAUDE.md, prd.md, rfc.md, api-contract.md, docs/04-adrs/ADR-*.md, plan-H<N>.md.

What problem does it solve?

Validates a pull request against the full SDD artifact chain (PRD, RFC, Contract, ADRs, Plan) and project rules (CLAUDE.md), helping teams ensure alignment and reduce regressions.

Core Features & Use Cases

  • Six-step review pipeline to verify consistency across PRD, RFC, and Contract.
  • Detects discrepancies between code and documentation and enforces CLAUDE.md rules.
  • Produces a structured review report with severity classifications (BLOCKER / WARNING / INFO) and a final verdict.

Quick Start

Copy the code-review skill into your repo's .github/skills or .claude/skills and trigger a PR review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate PR reviews against SDD artifacts like PRD and RFC documents?

Automated PR review validates your pull request diff against the full SDD artifact chain, including PRD, RFC, Contract, ADRs, and Plan files. It runs a six-step pipeline to verify consistency and enforces project rules defined in CLAUDE.md before merging.

Can I use CLAUDE.md rules to enforce code review standards in my repository?

Yes, CLAUDE.md rules are enforced during the pull request validation process. The review pipeline checks your PR diff against these project rules alongside the SDD artifacts to detect discrepancies between code and documentation.

How do I validate a pull request against an API contract and ADRs?

Validating a PR against an API contract and ADRs requires the PR diff and optional SDD artifacts like api-contract.md and docs/04-adrs/ADR-*.md. The review pipeline checks consistency across these documents and produces a structured report with severity classifications.

Do I need all SDD artifacts present to run a comprehensive PR validation?

No, only the PR diff and CLAUDE.md are required. Optional artifacts like PRD, RFC, Contract, ADRs, and Plan files enhance the review depth, but the pipeline applies to both greenfield and brownfield PRs even when some are missing.

What is the best way to get a structured review report for a pull request?

A structured review report is generated automatically after validating the PR against the SDD artifact chain. It includes severity classifications of BLOCKER, WARNING, and INFO, concluding with a final verdict to help teams ensure alignment and reduce regressions.

How do I set up automated SDD artifact validation in my GitHub repository?

Copy the code-review skill into your repo's .github/skills or .claude/skills directory to enable automated validation. Trigger a PR review to execute the six-step pipeline checking your diff against PRD, RFC, Contract, and CLAUDE.md rules.