What is a compliance score?

It is a mathematical percentage calculated by dividing the number of compliant requirements, error cases, and edge cases by the total requirements defined in your specification file.

Can it detect code that isn't in the specification?

Yes, the skill explicitly identifies 'Extra Features'—code that performs actions not mentioned in the spec—to help you decide if it's a helpful addition or unauthorized scope creep.

How does this differ from a regular code review?

While standard reviews focus on style and best practices, this skill focuses on 'Spec Validation'—verifying that the code actually performs the specific behaviors defined in your requirements document.

What happens if the code and specification don't match?

The skill generates a deviation report and recommends using the 'sdd:evolve' command to either update the specification to reflect the new reality or fix the code to match the original design.

SDD Code Reviewer

Name: SDD Code Reviewer
Author: rhuss

byrhuss

•

Security & Testing

Validates code implementations against technical specifications to ensure strict functional compliance and identify scope creep.

About

The review-code skill is a core component of Specification-Driven Development (SDD) for Claude Code. Unlike standard code reviews that focus primarily on style or quality, this skill rigorously compares the codebase against a formal specification file. It maps every functional requirement to specific lines of code, identifies deviations, and calculates a compliance score. This ensures that the final output perfectly matches the intended design, making it an essential tool for teams that require high process discipline and automated verification of business requirements.

Key Features

Comprehensive auditing of error handling and edge cases against spec definitions
Direct integration with 'sdd:evolve' to reconcile specification and code mismatches
1 GitHub stars
Scope creep detection to identify undocumented features not present in the spec
Automated compliance matrix mapping spec requirements to implementation files
Quantitative compliance scoring across functional and non-functional requirements

Use Cases

Auditing existing codebases against new documentation to ensure consistency
Enforcing rigorous adherence to API contracts and specific error response standards
Verifying a completed feature implementation before merging into a main branch

About

Key Features

Comprehensive auditing of error handling and edge cases against spec definitions
Direct integration with 'sdd:evolve' to reconcile specification and code mismatches
1 GitHub stars
Scope creep detection to identify undocumented features not present in the spec
Automated compliance matrix mapping spec requirements to implementation files
Quantitative compliance scoring across functional and non-functional requirements

Use Cases

Auditing existing codebases against new documentation to ensure consistency
Enforcing rigorous adherence to API contracts and specific error response standards
Verifying a completed feature implementation before merging into a main branch