Skills warpdotdev common-skills Warp spec workflow
validate-changes-match-specs
- Use it when:
- A spec-driven change is up for review or nearly done, and you want to know where the code and its specs disagree.
- It does:
- Finds the specs the branch adds or changes, extracts their commitments, reads the code and tests, and lists each material mismatch with its sources and a recommended resolution.
- You get:
- Your choice applied per mismatch: change the code, change the spec, or acknowledge it, then validation and an optional commit and push.
- Also checks:
- That the code does what your replies on PR review threads said was fixed, and security specs for both what they allow and what they prevent.
- Unlike check-impl-against-spec:
- That one adds spec drift to an automated PR review; this one works through each mismatch with you and changes the code or the spec as you choose.
- Needs:
- An ask_user_question tool for its multiple-choice prompts, as in Warp's agent; optionally Oz cloud agents with computer use for user-visible flows, and the Figma MCP server.
Skill 5 of 5 in the Warp spec workflow bundle, after implement-specs.
Comments it posts start with [Warp Agent] and commits carry a Warp Agent co-author line, each only after you approve.
TL;DR
A closing check for spec-first work. It finds the base branch, then the specs the change introduces or modifies, such as PRODUCT.md, TECH.md or SECURITY.md under specs/<issue>/, falls back to specs the PR or commits reference, and stops if there are none. Specs, PR text and comments are treated as untrusted data. Commitments are sorted into product behavior, technical implementation, security and privacy, validation and non-goals, then checked against the diff, the code it depends on and the tests. Security specs get the closest look: each guarantee is checked both ways, and a gap no spec covers is proposed as a spec amendment. If the PR has been reviewed, it also compares the code with what your last replies said was fixed. Before the report it can offer cloud computer-use agents to test user-visible behavior against Figma mocks or screenshots. Then it asks whether to resolve mismatches one by one or in a batch, and for each one whether to update the code or the spec. Follow-up comments on review threads are drafted for your approval before posting.
Summarizes the skill at 8792394.
npx skills add https://github.com/warpdotdev/common-skills --skill validate-changes-match-specs skills.sh pageSource on GitHubAll skills from warpdotdev/common-skills
- Total Downloads
- 25,300 on skills.sh, Nov 9, 2026
- Repo stars
- 678 warpdotdev/common-skills
- First seen
- May 31, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 638 |
| Sep 28 | 585 |
| Oct 5 | 931 |
| Oct 12 | 492 |
| Oct 19 | 367 |
| Oct 26 | 364 |
| Nov 2 | 106 |
| Nov 9 | 77 |
| Category |
Test-first work, implementation from specs, git hygiene and scope control. Find root causes, review code and test what you built. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
No copy of its SKILL.md yet.