bugfix-heavy
Skill1 starsChanged 5 months agoLicence not identifiedView on GitHub
Prescriptive 11-step bug fix workflow for COMPLEXA bugs and production incidents (cross-cutting concerns, persistence, concurrency, multi-user impact, business rules). Imported from Pulsar bugfix workflow per spec §21. Use when complexity classification is heavy or when bugfix-light auto-escalates at its complexity gate. Steps 1-3 subagent (recon + root-cause + domain truth model), 4 inline gate (controlled change proposal — REQUIRES APPROVAL), 5-6 inline (TDD pre-impl + minimal diff), 7 subagent (sanity + regression), 8 parallel subagents gate (adversarial security+architecture+quality), 9 subagent (post-fix UX E2E), 10 inline gate (Pa de Cal GO/NO-GO), 11 subagent (final after-all sanity sweep). Closes 4 audit gaps Heavy 3 (domain truth model net-new), Heavy 8 (3-way adversarial), Heavy 9 (UX as post-fix E2E), Heavy 11 (after-all distinct from Pa de Cal). Manual-only invocation via /pipeline-orchestrator:bugfix-heavy or via /pipeline-orchestrator:bugfix --heavy.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audit-heavySkill
- audit-lightSkill
- auditSkill
- bugfix-lightSkill
- bugfixSkill
- feature-heavySkill
- feature-lightSkill
- featureSkill
- measure-paperclip-fidelitySkill
- pipelineSkill
- refactor-heavySkill
- refactor-lightSkill
- refactorSkill
- reviewSkill
- spec-audit-onlySkill
- spec-designSkill
- spec-heavySkill
- spec-initSkill
- spec-lightSkill
- spec-requirementsSkill
- spec-reviewSkill
- specSkill
- spec-tasksSkill
- unblockSkill
- user-story-heavySkill
- user-story-lightSkill
- user-storySkill
- ux-sim-heavySkill
- ux-sim-lightSkill
- ux-simSkill
- validate-designSkill
- validate-gapSkill
- verify-completionSkill
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.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.