agentleFS
kunalsurikunalsuri/ai-fication-kit/.agents/skills/fix-bug/SKILL.md

fix-bug

Skill3 starsChanged 4 months agoApache-2.0View on GitHub

Fix a bug in this repository the safe way — reproduce first, failing regression test, root cause via the maps, surgical fix, review, ledger entry. Use whenever the user reports broken, wrong, or crashing behavior.

45 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 10 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

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.

    line 26
  2. Distinctive:

    Run the regression test (now green), then the suites covering the touched area.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 45 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
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Fix a bug

The contract: no fix before a reproduction, no reproduction without a failing test, no "fixed" without the regression test green, no closing without the ledger row and the gotcha recorded.

1. Reproduce

Draft ai/lab/specs/BUGFIX_<name>.md from BUGFIX_TEMPLATE.md: symptom (observed vs expected), exact reproduction steps. Get the user's OK.

2. Prove

Turn the reproduction into a regression test and watch it fail. A bug you cannot make a test fail for is a bug you do not understand yet. The test is permanent — it outlives the fix.

3. Locate

  • ai/guide/MODULE_MAP.md → which modules; note Stability of every suspect.
  • ai/guide/FEATURE_MAP.md gotchas + ai/lab/WORKLOG.md → was this area recently touched, or is the "bug" deliberate behavior a past ADR explains?
  • Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.

4. Gate

Root cause in a file with Stability frozen or ? ⇒ stop and ask the human. Record their approval in the bugfix doc before proceeding.

5. Diagnose, then fix

Name the root cause in the bugfix doc — the defect, not the symptom. Then make the smallest diff that turns the regression test green. Match the license headers of neighboring files. No drive-by refactors, no layout changes, no dependency additions while "in there".

6. Verify

Run the regression test (now green), then the suites covering the touched area. Report command run · exit status · failures verbatim. Red or unrun ⇒ not fixed.

7. Review & record

Request /review-change on the diff (fresh context — not this session). Append a bugfix row to ai/lab/WORKLOG.md linking the bugfix doc and review; add the gotcha line to FEATURE_MAP so the next agent knows the trap. All [inferred] — tell the user which tags await their [verified] flip.

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.