bug-fix
Skill0 starsChanged 7 months agoMITView on GitHub
Systematic bug diagnosis and fix. Use when debugging errors, unexpected behavior, or failing tests. Follows root-cause-first approach.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- eugenelim/agent-ready-repotheir own version, first seen Nov 8, 2026
- JosefGisis/skillstheir own version, first seen Nov 1, 2026
- callmeradical/skillstheir own version, first seen Nov 1, 2026
- GangJaeYu/harness_loop_full_koreantheir own version, first seen Oct 29, 2026
- phanijapps/memextheir own version, first seen Oct 17, 2026
Used with
Projects with it also use security-checklists, work-loop and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
eugenelimSkillsecurity-checklists
Progressive-disclosure security-depth modules for the security-reviewer. Holds ten boundary-keyed checklists (access-control, authn-session, injection, path-and-file, secrets-and-crypto, outbound-ssrf, supply-chain, config-misconfig, exceptional-conditions, llm-agent) as references/, each anchored on a current standard (OWASP Top 10:2025, ASVS 5.0, API Security Top 10:2023, Proactive Controls 2024, CWE Top 25, OWASP LLM Top 10:2025). The work-loop's orchestrator loads only the boundary-matching modules and inlines them into the security-reviewer's brief; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer reasons from.
Also in 3 projects that use this
- eugenelimSkill
work-loop
Use this skill whenever you're implementing a non-trivial change — a feature, a multi-file bug fix, a refactor, a migration, a framework or dependency upgrade, a schema or API change, performance work, an infrastructure or build-system edit, or anything spec-driven. It enforces the project's plan → execute → self-review → fix loop with mechanical gates (lint, typecheck, tests) and adversarial review. Default to this skill for any task larger than a one-line edit.
Also in 3 projects that use this
smileynetSkillimplementation
Game-specific coding guidance during implementation. Use when implementing game code, coding game mechanics, building game loop, setting up state machine, game architecture during development, writing game systems, structuring game update logic, or adding game input handling. Covers game loop setup, state management, input handling, frame budget, entity architecture, delta time.
Also in 3 projects that use this
dhzrxSkillprd-generator
Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products
Also in 3 projects that use this
DonTiziSkillnew-feature
Plan new features/integrations following SOLID principles. Analyzes codebase architecture, researches official documentation and best practices, designs extensible solution, and creates comprehensive GitHub issue with implementation blueprint.
Also in 3 projects that use this
SvampenSkillinit-project
Generates a tailored .claude/project-config.md for the current project. Asks about project type, quality check commands, documentation paths, insight tags, and review strictness.
Also in 3 projects that use this
- +1 more from eugenelim
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- techygarg/lattice★ 209same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- EmeaAppGbb/spec2cloud★ 100same name
- nwiizo/claudelytics★ 88same name
- eugenelim/agent-ready-repo★ 28same name
- Fadi88/one-man-startup★ 16same name
- eugenelim/llm-wiki-kit★ 12same name
- mae616/ai-template★ 9same name
- ramboz/jig★ 7same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- api-integrationSkill
- code-reviewSkill
- data-analysisSkill
- document-writerSkill
- refactorSkill
- test-generatorSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Never fix symptoms. If a null check "fixes" a crash, find why it's null.
- Distinctive: line 17
Read the error message. The answer is usually in the stack trace.
- Distinctive: line 18
Check git blame — when was this code last changed and by whom?
- Distinctive: line 20
Add a test that would have caught this bug.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bug Fix
Process
- Reproduce — confirm the bug exists, get exact error/behavior
- Isolate — narrow to the smallest code path that triggers it
- Root cause — find the actual cause, not just the symptom
- Fix — change the minimum code needed
- Verify — confirm the fix works AND doesn't break anything else
Rules
- Never fix symptoms. If a null check "fixes" a crash, find why it's null.
- Read the error message. The answer is usually in the stack trace.
- Check git blame — when was this code last changed and by whom?
- One fix per bug. Don't refactor while fixing.
- Add a test that would have caught this bug.
Output
- Root cause: one sentence explaining why the bug exists
- Fix: the minimal code change
- Test: how to verify the fix
- Prevention: what would catch this class of bug in the future
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.