agentleFS
Sign inStart free
YehudaFrankelYehudaFrankel/clankbrain/.claude/skills/fix-bug/SKILL.md

fix-bug

Skill16 starsChanged 7 months agoMITView on GitHub

Use when the user reports a LOGIC bug — wrong behavior, incorrect output, or a feature not working as designed. Triggers on "fix the bug where", "it's broken", "not sending", "not saving", "wrong result", "something broke".

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use improvement, build-feature and 8 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.
  • kiminmonacoSkill

    improvement

    Guide for making improvements to existing ClaudeBar functionality using TDD. Use this skill when: (1) Enhancing existing features (not adding new ones) (2) Improving UX, performance, or code quality (3) User asks "improve X", "make Y better", or "enhance Z" (4) Small enhancements that don't require full architecture design For NEW features, use implement-feature skill instead.

    Also in 4 projects that use this

  • sirakinbSkill

    build-feature

    Autonomous task loop that picks ready tasks, implements them, updates progress.txt, commits, and repeats. Use when asked to 'build feature', 'run the loop', or 'implement these tasks'.

    Also in 5 projects that use this

  • kiminmonacoSkill

    implement-feature

    Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers

    Also in 7 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 6 projects that use this

  • JetBrainsSkill

    create-plan

    Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.

    Also in 4 projects that use this

  • JasonPaffSkill

    implement-plan

    Execute implementation plan with structured tracking and validation using subagent architecture

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After step 8 — automatically run the following WITHOUT waiting for user to ask:

    line 36
  2. Distinctive:

    Run the verification or smoke-test skill on the changed file(s)

    line 39
  3. Distinctive:

    Only stop when verification reports all checks passed

    line 40
  4. Very specific:

    Run the guard skill on the changed file(s)

    line 43

“Common” is measured: kept by at least 6 in 10 of the 40 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

Fix Bug

  1. Locate the failure layer — ask: is it frontend, API/backend, database, scheduler, or email?
  2. Read the relevant file — don't guess; read it with offset+limit if large
  3. Hypothesize one root cause — state it before touching anything:

    "I think the issue is X because Y"

  4. Check common silent failure modes first:
    • Build artifact not updated after source change (cache, compiled output, stale class)
    • Wrong variable scope (session/context object used in wrong method)
    • Missing auth/ownership check silently filtering the record out
    • INSERT missing required fields → row created but invisible
    • Query missing tenant/org filter → returns wrong user's data
    • Async callback firing before data is ready
  5. Fix only the confirmed root cause — minimum code change
  6. Verify — re-test the exact failing case, confirm nothing adjacent broke
  7. Log it — if tasks/error-lookup.md exists, add one line to it (otherwise skip this step): [date] | error description | root cause | fix applied
  8. Report: "Bug fixed. Root cause was: [X]. Changed: [file:line]. Verified: [how]."

Auto-Chain

After step 8 — automatically run the following WITHOUT waiting for user to ask:

Step A — Verification:

  • Run the verification or smoke-test skill on the changed file(s)
  • Only stop when verification reports all checks passed

Step B — Guard (always, after any fix):

  • Run the guard skill on the changed file(s)
  • Guard will scan for known error patterns AND log the root cause as a new permanent rule
  • This ensures the same class of error can never ship again

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.

Check your setup, free