Validate Changes Match Specs

A thorough spec compliance checker that walks through product, technical, and security commitments line by line. It diffs your branch against whatever specs you introduced or changed, extracts concrete promises from docs under specs/, then compares them against actual code, tests, and validation artifacts. The security validation is especially aggressive: it checks both that safe behavior exists and that unsafe behavior is blocked, looking for gaps in auth boundaries, data exposure, and tenant isolation. If your PR already has review comments, it cross-checks whether you actually delivered what you said you'd fix. The mismatch-by-mismatch resolution flow keeps you honest about whether to update code or walk back the spec.

skills.sh installs: 25.3K
GitHub stars: 684
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add warpdotdev/common-skills --skill validate-changes-match-specs --agent claude-code

Installs into .claude/skills of the current project.

Files

Validate changes match specs

Use this skill to verify that a branch or pull request implements the behavior and design promised by its specs. The workflow finds specs introduced by the change, compares them against code, tests, documentation, and validation artifacts, then walks the user through every material mismatch.

Goals

Find specs introduced or modified by the current change.
Extract concrete product, technical, security, migration, rollout, and validation commitments.
Compare those commitments against the actual implementation.
Produce a clear mismatch list.
Ask the user, mismatch by mismatch, whether to update the implementation to match the spec or update the spec to match the implementation.
Apply the chosen resolutions either one-by-one or in a batch.

Spec discovery

Start by identifying the base branch and changed files.

Prefer repository conventions when known. Otherwise:

Use the PR base branch when a PR exists.
Use main, master, or develop only when that is clearly the repository's base branch.
Use git merge-base and git diff --name-only <base>...HEAD to find files introduced or modified by the branch.

SKILL.md on GitHub