agentleFS
Sign inStart free
sp1esp1e/claude-skills/gsd-debug/SKILL.md

gsd-debug

Skill1 starsChanged 31 days agoMITView on GitHub

Systematic debugging with persistent state across context resets

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 3

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    If $ARGUMENTS starts with "list": SUBCMD=list, no further args

    line 40
  2. Common:

    If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)

    line 41
  3. Common:

    If $ARGUMENTS starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)

    line 42
  4. Very specific:

    If $ARGUMENTS contains --diagnose: SUBCMD=debug, diagnose_only=true, strip --diagnose from description

    line 43
  5. Very specific:

    Check for active sessions (used for non-list/status/continue flows):

    line 46

“Common” is measured: kept by at least 6 in 10 of the 4 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
<objective> Debug issues using scientific method with subagent isolation.

Orchestrator role: Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.

Flags:

  • --diagnose — Diagnose only. Returns a Root Cause Report without applying a fix.

Subcommands: list · status <slug> · continue <slug> </objective>

<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):

  • gsd-debug-session-manager — manages debug checkpoint/continuation loop in isolated context
  • gsd-debugger — investigates bugs using scientific method </available_agent_types>

<execution_context> @$HOME/.claude/get-shit-done/workflows/debug.md </execution_context>

<context> User's input: $ARGUMENTS

Parse subcommands and flags from $ARGUMENTS BEFORE the active-session check:

  • If $ARGUMENTS starts with "list": SUBCMD=list, no further args
  • If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)
  • If $ARGUMENTS starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)
  • If $ARGUMENTS contains --diagnose: SUBCMD=debug, diagnose_only=true, strip --diagnose from description
  • Otherwise: SUBCMD=debug, diagnose_only=false

Check for active sessions (used for non-list/status/continue flows):

ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
</context><process> Execute end-to-end. </process>

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