speckit-bugfix-verify
Skill1 starsChanged 3 days agoApache-2.0View on GitHub
Verify that bugfix patches are consistent across all spec artifacts
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autopilot-supervisorSkill
- reclaim-diskSkill
- speckit-analyzeSkill
- speckit-autopilotSkill
- speckit-bugfix-patchSkill
- speckit-bugfix-reportSkill
- speckit-bugfix-switchSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-docguard-diagnoseSkill
- speckit-docguard-fixSkill
- speckit-docguard-generateSkill
- speckit-docguard-guardSkill
- speckit-docguard-reviewSkill
- speckit-docguard-scoreSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-tdd-planSkill
- speckit-tdd-runSkill
- speckit-tdd-setupSkill
- speckit-tdd-verifySkill
- visual-passSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Verify that all spec artifacts are consistent after bugfix patches — checks that new requirements have corresponding plan sections and …
- Very specific: line 31
Verify a spec-kit project exists by checking for .specify/ directory
- Very specific: line 33
Verify at least spec.md exists
- Distinctive: line 37
Load all artifacts: Read from the current feature directory:
- Distinctive: line 54
No duplicate requirements introduced by the patch
- Distinctive: line 58
Every new requirement in spec.md has a corresponding plan section or note
- Distinctive: line 59
No plan sections reference removed or superseded requirements
- Distinctive: line 63
Every new requirement in spec.md is traceable to at least one task
- Very specific: line 64
No tasks marked [x] that were supposed to be reopened
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bugfix Verify Skill
Verify Bugfix Consistency
Verify that all spec artifacts are consistent after bugfix patches — checks that new requirements have corresponding plan sections and tasks, reopened tasks are not still marked complete, and no orphaned references exist.
User Input
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty). The user may specify a bug ID to verify (e.g., "BUG-001") or "all" to check everything.
Prerequisites
- Verify a spec-kit project exists by checking for
.specify/directory - Locate the current feature's spec directory
- Verify at least
spec.mdexists
Outline
- Load all artifacts: Read from the current feature directory:
spec.md— the source of truthplan.md— implementation plan (if exists)tasks.md— task breakdown (if exists)specs/{feature}/bugs/*.md— all bug reports
Check bug report status: For each bug report file:
Check Pass Condition Fail Condition Report exists Bug file is in bugs/directoryMissing bug file Report is patched Has **Status**: PatchedmarkerStill Openor missing statusPatch date present Has **Patched**: [DATE]entryMissing patch date - Verify spec.md consistency: For each bugfix note in spec.md:
- New requirements have clear acceptance criteria
- Strikethrough items have a reason documented
- No duplicate requirements introduced by the patch
- Bug IDs in notes match existing bug report files
- Verify plan.md consistency (if exists):
- Every new requirement in spec.md has a corresponding plan section or note
- No plan sections reference removed or superseded requirements
- Bugfix notes in plan.md match those in spec.md
- Verify tasks.md consistency (if exists):
- Every new requirement in spec.md is traceable to at least one task
- No tasks marked
[x]that were supposed to be reopened - Reopened tasks have the
(reopened — BUG-NNN)annotation - New task IDs are sequential and do not duplicate existing IDs
- Task dependencies form a valid DAG (no circular dependencies)
- Wave DAG (if present) includes all new tasks
Output verification report:
# Bugfix Verification Report **Feature**: [Feature name] **Date**: [DATE] ## Bug Reports | Bug ID | Title | Status | Patched | |--------|-------|--------|---------| | BUG-001 | [Title] | ✅ Patched | [DATE] | | BUG-002 | [Title] | ⚠️ Open | — | ## Consistency Checks | Check | Result | Details | |-------|--------|---------| | All bugs patched | ✅ Pass / ⚠️ Fail | [N patched, M open] | | Spec requirements covered | ✅ Pass / ⚠️ Fail | [N requirements, all have tasks] | | No false completions | ✅ Pass / ⚠️ Fail | [N tasks verified] | | Reopened tasks annotated | ✅ Pass / ⚠️ Fail | [N reopened, all annotated] | | Task IDs sequential | ✅ Pass / ⚠️ Fail | [Last ID: TNNN] | | No circular dependencies | ✅ Pass / ⚠️ Fail | [DAG valid] | | Cross-artifact traceability | ✅ Pass / ⚠️ Fail | [All specs → plan → tasks] | ## Recommended Actions - [List any issues found and how to fix them] - If all checks pass: Resume `/speckit.implement` to apply the code fix- Report: Output the verification report. Do not modify any files — this command is read-only.
Rules
- Read-only — this command never modifies any files
- Check all artifacts — verify consistency across spec, plan, tasks, and bug reports
- Be specific about failures — report exact bug IDs, task IDs, and requirement text that fail checks
- Handle missing artifacts gracefully — if plan.md or tasks.md does not exist, skip those checks and note the absence
- Verify traceability — every bugfix note must reference a valid bug report, and every bug report must have corresponding artifact changes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

