backbay-labs/thrunt-god/thrunt-debug

Claude Code and agent skill by backbay-labs/thrunt-god

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Systematic debugging with persistent state across context resets

Install

npx vskill@latest install backbay-labs/thrunt-god/thrunt-debug

SKILL.md

The same SKILL.md was published earlier as backbay-labs/thrunt-god/thrunt-debug.

<objective> Debug issues using scientific method with subagent isolation.

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

Why subagent: Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction. </objective>

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

  • thrunt-incident-debugger — Diagnoses and fixes issues

</available_agent_types>

<context> User's issue: $ARGUMENTS

Check for active sessions:

bash
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5

</context>

<process>

0. Initialize Context

bash
INIT=$(node ".github/thrunt-god/bin/thrunt-tools.cjs" state load)
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi

Extract commit_docs from init JSON. Resolve debugger model:

bash
debugger_model=$(node ".github/thrunt-god/bin/thrunt-tools.cjs" resolve-model thrunt-incident-debugger --raw)

1. Check Active Sessions

If active sessions exist AND no $ARGUMENTS:

  • List sessions with status, hypothesis, next action
  • User picks number to resume OR describes new issue

If $ARGUMENTS provided OR user describes new issue:

  • Continue to symptom gathering

2. Gather Symptoms (if new issue)

Use AskUserQuestion for each:

  1. Expected behavior - What should happen?
  2. Actual behavior - What happens instead?
  3. Error messages - Any errors? (paste or describe)
  4. Timeline - When did this start? Ever worked?
  5. Reproduction - How do you trigger it?

After all gathered, confirm ready to investigate.

3. Spawn thrunt-incident-debugger Agent

Fill prompt and spawn:

markdown
<objective>
Investigate issue: {slug}
**Summary:** {trigger}
</objective>
<symptoms>
expected: {expected}
actual: {actual}
errors: {errors}
reproduction: {reproduction}
timeline: {timeline}
</symptoms>
<mode>
symptoms_prefilled: true
goal: find_and_fix
</mode>
<debug_file>
Create: .planning/debug/{slug}.md
</debug_file>
Task(
prompt=filled_prompt,
subagent_type="thrunt-incident-debugger",
model="{debugger_model}",
description="Debug {slug}"
)

4. Handle Agent Return

If `## ROOT CAUSE FOUND`:

  • Display root cause and evidence summary
  • Offer options:
  • "Fix now" - spawn fix subagent
  • "Plan fix" - suggest /hunt-plan --gaps
  • "Manual fix" - done

If `## CHECKPOINT REACHED`:

  • Present checkpoint details to user
  • Get user response
  • If checkpoint type is human-verify:
  • If user confirms fixed: continue so agent can finalize/resolve/archive
  • If user reports issues: continue so agent returns to investigation/fixing
  • Spawn continuation agent (see step 5)

If `## INVESTIGATION INCONCLUSIVE`:

  • Show what was checked and eliminated
  • Offer options:
  • "Continue investigating" - spawn new agent with additional context
  • "Manual investigation" - done
  • "Add more context" - gather more symptoms, spawn again

5. Spawn Continuation Agent (After Checkpoint)

When user responds to checkpoint, spawn fresh agent:

markdown
<objective>
Continue debugging {slug}. Evidence is in the debug file.
</objective>
<prior_state>
<files_to_read>
-.planning/debug/{slug}.md (Debug session state)
</files_to_read>
</prior_state>
<checkpoint_response>
**Type:** {checkpoint_type}
**Response:** {user_response}
</checkpoint_response>
<mode>
goal: find_and_fix
</mode>
Task(
prompt=continuation_prompt,
subagent_type="thrunt-incident-debugger",
model="{debugger_model}",
description="Continue debug {slug}"
)

</process>

<success_criteria>

  • [ ] Active sessions checked
  • [ ] Symptoms gathered (if new)
  • [ ] thrunt-incident-debugger spawned with context
  • [ ] Checkpoints handled correctly
  • [ ] Root cause confirmed before fixing

</success_criteria>

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
30
Repository forks
5
Repository npm downloads, 7 days
15
7-day trend score
33

Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 30 Apr 2026, 6 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/backbay-labs/thrunt-god/thrunt-debug/badge)](https://verified-skill.com/skills/backbay-labs/thrunt-god/thrunt-debug)

Something wrong with this skill or its page? Tell us.