speckit-bugfix-switch
Skill1 starsChanged 3 days agoApache-2.0View on GitHub
Switch to a different bugfix context
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-verifySkill
- 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
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 16
Update current context into existing feature.
- Very specific: line 27
Check specs/{feature} dir exists, report an error to user if missing.
- Distinctive: line 31
If current branch contains uncommitted changes STOP immediately and escalate to project maintainers for guidance.
- Very specific: line 34
Update .specify/feature.json with specs/{feature}
- Very specific: line 37
Update the plan reference between the <!-- SPECKIT START --> and <!-- SPECKIT END --> markers in .github/copilot-instructions.md to point …
≈ “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 Switch Skill
Switch bugfix context
Update current context into existing feature. The feature identity is define by user.
User Input
$ARGUMENTSOutline
- Validate feature:
- Check
specs/{feature}dir exists, report an error to user if missing.
- Check
- Checkout feature branch:
- Checkout a new
{feature}branch using git command, always use main branch as source. - If current branch contains uncommitted changes STOP immediately and escalate to project maintainers for guidance.
- Checkout a new
- Feature context update:
- Update
.specify/feature.jsonwithspecs/{feature}
- Update
- Agent context update:
- Update the plan reference between the
<!-- SPECKIT START -->and<!-- SPECKIT END -->markers in.github/copilot-instructions.mdto point to the feature plan filespecs/{feature}/plan.md
- Update the plan reference between the
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.

