Skip to content

Cristhianzl/claude-skills-czl / configs/agnostic/skills/debugging-agent-runs

debugging-agent-runs

Verified

Recover when the AGENT itself is stuck — looping, repeating the same failed action, burning tokens/budget, overflowing context, drifting from the goal, or acting on stale state. Use when a run isn't converging and reworded retries aren't helping. This is a workflow you follow, not a hidden runtime that auto-heals. For bugs in the product code use fixing-bugs.

Debugging agent runs

When the problem is the run, not the code: the agent keeps trying variations of the same thing, talks itself in circles, or acts on what it remembers instead of what's true. This skill is a recovery loop to break that. Be honest: it's a discipline you apply — it can't magically fix a stuck process.

Read first (always)

List learnings/ and read anything relevant — past failure modes specific to this project belong there.

Recognize the failure mode

SymptomLikely cause
Same action retried with slightly reworded promptsLoop / no new information between attempts
Output truncated, "forgetting" earlier contextContext overflow → compact or restart with a tighter scope
Repeated 429 / timeoutsRate limit → back off, batch, slow down
Edits land on the wrong branch/files; conflictsBranch / diff drift → re-verify git state
Confident claims that don't match realityStale state → trusting memory over the world
Scope keeps widening while nothing landsScope creep → shrink to one verifiable thing

The recovery loop

Run these in order — most stuck runs are fixed by step 1–2:

  1. Restate the real objective in one sentence. If you can't, that's the bug. Re-anchor to the user's actual goal, not the sub-task you spiraled into.
  2. Verify world state — don't trust memory. Re-read the files, git status/diff, and the actual test/command output. The model's recollection is often stale; reality isn't.
  3. Shrink the failing scope. Reduce to the smallest reproduction or the single failing unit. Big scope hides the cause.
  4. Run one discriminating check — the single command/test whose result tells you which branch of the problem you're in. Don't guess; get one new bit of information.
  5. Only then retry — and change the approach, not just the wording. If the new info didn't change your plan, you're still looping.

Anti-patterns

  • Retrying the same action three times with reworded prompts (no new information = a loop).
  • Trusting your memory of the code/state instead of re-reading it.
  • Widening scope when stuck (the opposite of step 3).
  • Fabricating that something "should now work" without a check that proves it.

When to stop and ask the human

After one full recovery pass with no progress — or on a budget/rate-limit wall — stop and surface it: the objective, what you verified, the one check you ran, and where it's blocked. A clear handoff beats more silent retries.

Capture a learning

If a project-specific failure mode or recovery trick shows up, append a learnings/YYYY-MM-DD-slug.md (or use /learn).

See also

  • skills/fixing-bugs — once you've isolated a real code bug, switch to the reproduce-first fix workflow.
  • skills/running-agent-loops — stop conditions and escalation for unattended loops.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall