bug-squashing-methodology
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Structured 6-step bug fix process with reproduction, root cause analysis, and TDD. Use when fixing bugs, debugging failures, or investigating defects. Covers reproduction, RCA documentation, TDD fix cycle, and PR workflow. Do NOT use for general feature development (use stay-green), CI environment issues (use ci-debugging), code reviews (use comprehensive-pr-review), or general git workflow like issue creation, branching, and PRs (use git-workflow).
In this repository36 other files it gives its agents.
- address-feedbackSkill
- apple-to-android-port-specSkill
- architectural-decisionsSkill
- await-claude-reviewSkill
- backlog-groomingSkill
- ci-debuggingSkill
- collect-skillsSkill
- comprehensive-pr-reviewSkill
- concurrencySkill
- continue-epicSkill
- cve-remediationSkill
- de-slopifySkill
- discord-ralph-recapSkill
- distribute-skillsSkill
- documentationSkill
- error-handlingSkill
- file-naming-conventionsSkill
- frontend-aestheticsSkill
- git-workflowSkill
- max-quality-no-shortcutsSkill
- mutation-testingSkill
- preflightSkill
- prompt-engineeringSkill
- quick-testSkill
- review-diffSkill
- scan-issue-writerSkill
- securitySkill
- skill-craftSkill
- spec-decompositionSkill
- statusSkill
- stay-greenSkill
- testingSkill
- tracer-codeSkill
- triage-and-planSkill
- user-facing-error-messagesSkill
- vibeSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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.