agentleFS
kapadiaskapadias/nonna/.claude/skills/debugging/SKILL.md

debugging

Skill0 starsChanged 46 days agoMITView on GitHub

Chasing a bug, regression, or failing test to root cause: deterministic repro, bisection, minimal fix, proof. Used by /debug and the debugger agent.

121 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use Problem-Solving Techniques, media-processing 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.
  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 4 projects that use this

  • mrgoonieSkill

    media-processing

    Process multimedia files with FFmpeg (video/audio encoding, conversion, streaming, filtering, hardware acceleration) and ImageMagick (image manipulation, format conversion, batch processing, effects, composition). Use when converting media formats, encoding videos with specific codecs (H.264, H.265, VP9), resizing/cropping images, extracting audio from video, applying filters and effects, optimizing file sizes, creating streaming manifests (HLS/DASH), generating thumbnails, batch processing images, creating composite images, or implementing media processing pipelines. Supports 100+ formats, hardware acceleration (NVENC, QSV), and complex filtergraphs.

    Also in 6 projects that use this

  • JetBrainsSkill

    ssr

    Guide for using Structural Search and Replace in IntelliJ. Use when creating or modifying SSR inspections or search patterns.

    Also in 3 projects that use this

  • mrgoonieSkill

    web-frameworks

    Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.

    Also in 6 projects that use this

  • DevNewbie1826Skill

    remove-ai-slops

    Remove AI-generated code slop from branch changes or an explicit file list while preserving behavior, including junk tests (prose pins, source greps, copied inventories, mock echoes), each proven by its class rule before a cut. Use when asked to remove slop, clean AI code, deslop, clean up generated code, strip slop, prune junk tests, or review generated-code cleanup. Start by locking behavior with regression tests, then use the workflow and category references.

    Also in 3 projects that use this

  • DevNewbie1826Skill

    programming

    MUST USE for work on Python, Rust, TypeScript, JavaScript, or Go source files and project manifests, and whenever a test or spec file is written, reshaped, reviewed, or deleted. Triggers: write or edit code; add, change, or delete a test; test authoring gate; junk tests; new project; Go HTTP service (gin lane); Bubble Tea TUI; CJK IME; Connect-Go RPC; sqlc or pgx; branded IDs; exhaustive matching; unsafe Rust; Miri; oversized file; refactoring; logging, log levels, structured logging, or observability; arena, allocator, bumpalo, const fn, const generics, compile-time programming, zero-allocation APIs, bitfields, repr, scope guards, errdefer-style cleanup, Zig-like patterns, zero-copy parsing, packed data, or FFI; Rust public API design or macros.

    Also in 3 projects that use this

  • +6 more from mrgoonie

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

    If you can't fill in X, Y, and Z, you haven't found it — keep isolating.

    line 41
  2. Distinctive:

    Read it as a timeline: classify by the exception type, find the throw site, then trace the bad value

    line 61

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

Debugging

Find the cause, not a quieter symptom. A bug you patched without understanding is a bug you will meet again under a worse condition. Trust evidence over intuition — the code does what it does, not what you remember writing.

The method: Reproduce → Isolate → Diagnose → Fix → Prove

1. Reproduce

Make it happen on demand. An intermittent bug you cannot trigger is a bug you cannot fix or verify. Drive the repro down to the smallest deterministic input. Ideally, encode it as a failing test — that test is now both your reproduction and your future regression guard. If you can't reproduce it, you're not debugging yet; you're guessing.

2. Isolate

Form a hypothesis, then run an experiment that can falsify it. Binary-search the fault:

  • History: git bisect across commits — "what changed since it last worked?" is the single most productive question. Bisect finds the commit in log₂(n) steps. The bundled helper scripts/bisect.sh automates the whole run: bisect.sh <good-ref> <test-command...>, where the test command exits 0 when the bug is absent and non-zero when present.
  • Input: halve the failing input until the minimal trigger remains.
  • Code path: disable/short-circuit halves of the pipeline to localize the stage.

Change one variable at a time. If you change three things and it works, you've learned nothing.

3. Diagnose

State the root cause in one sentence before touching the fix:

"The bug is X (a stale cache key), which causes Y (a deleted record reappears) under condition Z (two writes within the TTL window)."

If you can't fill in X, Y, and Z, you haven't found it — keep isolating. A fix applied before diagnosis is a coin flip.

4. Fix minimally

Fix the cause, not the symptom, with the smallest diff that removes it. A report names a symptom. Before you edit, grep every caller of the function you are about to touch and fix the shared function once — one guard where all callers route through is a smaller diff than one per caller, and patching only the path the ticket names leaves a sibling caller still broken. Don't refactor surrounding code in the same change — a fix commit should be reviewable as exactly the fix. If the real fix is large, note it and do the surgical version now; schedule the rest.

5. Prove

  • The regression test from step 1 now passes.
  • The full suite is green — you fixed it without breaking a neighbor.
  • Nothing was masked. You didn't make the failure invisible; you made it not happen.

Reading a stack trace

Read it as a timeline: classify by the exception type, find the throw site, then trace the bad value backward to its origin — the throw is the symptom, the line that set up the value is the cause. Ordering and chaining differ per language (Python fails at the bottom; Java/JS at the top); see references/stack-traces.md for worked examples across Python, the JVM, and async Node.

Anti-patterns

  • Symptom-patching. Adding a null-check where it blew up instead of asking why the value was null. The cause moves downstream and returns.
  • Patching the named path. Guarding the one caller in the ticket while three siblings still hit the bug. Fix it where all callers route through.
  • Broadening a catch. Wrapping a wider try to make an exception disappear hides the next bug too. Catch narrowly, at the layer that can actually handle it.
  • Silencing what you don't understand. Swallowing an error or downgrading a log to make red go away is hiding a fire, not putting it out. (.claude/rules/safety.md — never fail open.)
  • Weakening a test to go green. Loosening an assert or deleting a case to pass is sabotage of the one thing protecting capital. The test was right; the code is wrong.
  • Debugging by random edit. Changing things hoping the symptom shifts. Without a hypothesis you're not learning — you're rolling dice and corrupting state.

Route through the debugger agent and /debug. When the cause is found, the regression test ships with the fix — that's how the same bug never bills you twice.

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.