agentleFS
Sign inStart free
nanosite-ainanosite-ai/nanoflow/skills/fix-bug/SKILL.md

fix-bug

Skill15 starsChanged 33 days agoMITView on GitHub

Fix a bug by reproducing it with a failing test first, finding the root cause, and watching the same test pass. Use for any bug report, regression, or "this is broken" request.

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

3 rules. 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    only in the browser (refresh, cookies, navigation, hydration) → an e2e test (Playwright).

    line 16
  2. Distinctive:

    Name the root cause in one sentence: before editing. Trace the real path and fix the cause, in the layer it lives in, not where it surfaced.

    line 21
  3. Distinctive:

    If a bug truly can't be reproduced by a test, say so and why before patching, and put the manual reproduction and verification on the …

    line 30

“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 a bug: failing test first

A fix you can't show failing-then-passing is a guess. The reproducing test stays in the suite as a permanent guard.

  1. Ticket. nf task start --new "<symptom in plain words>" --type bug --definition "<symptom>" --plan "<steps to reproduce>" (or claim the existing issue). Work in the worktree it creates.

  2. Reproduce with a failing test at the lowest layer that shows it.

    • pure logic → a unit test next to the file;
    • API / database / auth → an integration test;
    • only in the browser (refresh, cookies, navigation, hydration) → an e2e test (Playwright).

    Assert the correct behaviour, run only that test, and watch it fail.

  3. Check it fails for the reported reason. A test that fails for another reason, or passes before any change, is testing the wrong thing. Fix the test first.
  4. Name the root cause in one sentence before editing. Trace the real path and fix the cause, in the layer it lives in, not where it surfaced.
  5. Fix it, minimally.
  6. Watch the same test pass, unchanged. (nanoflow shows a "now passes" toast when a red check turns green.)
  7. Run the repo's checks: nf check. All green, or it isn't done.
  8. Record it on the ticket, in this order: Symptom → Reproduction → Root cause (with reasoning) → Fix (why it resolves the cause; alternatives considered) → Testing (the guarding test, and how you verified). Then nf pr create.

If a bug truly can't be reproduced by a test, say so and why before patching, and put the manual reproduction and verification on the ticket instead. Don't bundle unrelated refactors into a bug fix.

<sub>Part of nanoflow by nanosite.ai.</sub>

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