Stats
Actions
Tags
From superkit
Before code review, checks the branch diff against the spec's acceptance criteria and produces an advisory met/unmet/uncertain checklist for the human reviewer. Non-blocking. Use at the end of executing a superkit/spec-kit feature, just before requesting-code-review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/superkit:conformance-checkThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Catch "tests pass but it didn't build what was asked." Runs just before
Catch "tests pass but it didn't build what was asked." Runs just before
superpowers:requesting-code-review. Advisory only — never blocks.
specs/<id>/spec.md and extract its acceptance criteria /
requirements.git diff <base>...HEAD (the feature branch's diff against its base).
Scope discipline (superkit:respecting-the-spec-contract): use ONLY the criteria + the diff.
Do not load the whole specs//.superkit/ tree.Dispatch ONE subagent (Task) given only the acceptance criteria and the diff. It maps each criterion to met / unmet / uncertain with a one-line justification citing the diff.
Present the checklist to the user as part of the review hand-off, e.g.:
Conformance vs spec.md acceptance criteria:
- [met] Criterion A — <why>
- [unmet] Criterion B — <why>
- [uncertain] Criterion C — <why>
This is advisory: surface unmet/uncertain items so the human reviewer can decide. Do NOT block the pipeline or loop to fix them automatically.
npx claudepluginhub joshuatrobertson/super-kit --plugin superkitGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.