bug-fix
Skill88 starsChanged 8 months agoMITView on GitHub
Systematic bug investigation and fix workflow. Use when fixing bugs, investigating issues, or debugging test failures.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- ceilidhboy/skillstheir own version, first seen Nov 15, 2026
- eugenelim/agent-ready-repotheir own version, first seen Nov 14, 2026
- paureis/pau-skillstheir 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
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
eugenelimSkillwork-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 versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- techygarg/lattice★ 209same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- EmeaAppGbb/spec2cloud★ 100same name
- eugenelim/agent-ready-repo★ 31same name
- Fadi88/one-man-startup★ 16same name
- eugenelim/llm-wiki-kit★ 12same name
- mae616/ai-template★ 9same name
- ramboz/jig★ 7same name
- crgarcia12/Liliput★ 4same name
16 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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- deploy-checkSkill
- dev-setupSkill
- orchestratorSkill
- pre-release-checkSkill
- qa-pipelineSkill
- refactor-analysisSkill
- refactorSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
4
Distinctive
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
- Very specific: line 13
Search for related issues: gh issue list --label bug
- Very specific: line 14
Search error patterns: rg "unwrap\(\)|expect\(" src/ and rg "TODO|FIXME" src/
- Distinctive: line 20
Create a minimal failing test:
- Very specific: line 27
Verify the issue: cargo test test_reproduce_issue -- --nocapture
- Distinctive: line 40
Add a failing test first
- Distinctive: line 42
Verify the test passes
- Distinctive: line 55
Add a dedicated regression test to prevent recurrence:
“Common” is measured: kept by at least 6 in 10 of the 20 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 Workflow
Fix $ARGUMENTS using this systematic process.
Step 1: Investigation (parallel)
- Search for related issues:
gh issue list --label bug - Search error patterns:
rg "unwrap\(\)|expect\(" src/andrg "TODO|FIXME" src/ - Review recent commits for potential causes:
git log --oneline -20
Step 2: Reproduction
- Extract error messages and affected context
- Create a minimal failing test:
#[test] fn test_reproduce_issue() { // Minimal reproduction } - Verify the issue:
cargo test test_reproduce_issue -- --nocapture
Step 3: Root Cause Analysis
Common categories in this project:
- Parsing: Malformed JSONL handling
- Date/Time: Timezone or format issues
- Paths: Cross-platform path handling
- Memory: Large file processing
- Display: Terminal width/color issues
Step 4: Fix Implementation
- Add a failing test first
- Implement the fix
- Verify the test passes
- Check for regressions
Step 5: Verification
cargo test <specific_test>
cargo test
cargo test --all-featuresStep 6: Regression Prevention
Add a dedicated regression test to prevent recurrence:
#[cfg(test)]
mod regression_tests {
#[test]
fn issue_NNN_description() {
// Ensure this specific issue doesn't reoccur
}
}Checklist
- Issue reproduced locally
- Root cause identified
- Fix implemented with tests
- No regressions introduced
- Performance impact assessed
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.

