agentleFS
nwiizonwiizo/claudelytics/.claude/skills/bug-fix/SKILL.md

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

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.
  • eugenelimSkill

    security-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

  • smileynetSkill

    implementation

    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

  • dhzrxSkill

    prd-generator

    Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products

    Also in 3 projects that use this

  • DonTiziSkill

    new-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

  • SvampenSkill

    init-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

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
  1. Very specific:

    Search for related issues: gh issue list --label bug

    line 13
  2. Very specific:

    Search error patterns: rg "unwrap\(\)|expect\(" src/ and rg "TODO|FIXME" src/

    line 14
  3. Distinctive:

    Create a minimal failing test:

    line 20
  4. Very specific:

    Verify the issue: cargo test test_reproduce_issue -- --nocapture

    line 27
  5. Distinctive:

    Add a failing test first

    line 40
  6. Distinctive:

    Verify the test passes

    line 42
  7. Distinctive:

    Add a dedicated regression test to prevent recurrence:

    line 55

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/ and rg "TODO|FIXME" src/
  • Review recent commits for potential causes: git log --oneline -20

Step 2: Reproduction

  1. Extract error messages and affected context
  2. Create a minimal failing test:
    #[test]
    fn test_reproduce_issue() {
        // Minimal reproduction
    }
  3. 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

  1. Add a failing test first
  2. Implement the fix
  3. Verify the test passes
  4. Check for regressions

Step 5: Verification

cargo test <specific_test>
cargo test
cargo test --all-features

Step 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.