debugger

Trace bugs backward through call stacks to identify original triggers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/towry/dots --skill debugger-towry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/towry/dots/tree/main/conf/claude-local-marketplace/skills/debugger
Command: npx skills add https://github.com/towry/dots --skill debugger-towry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves?

This skill provides a structured, systematic approach to debugging complex and elusive issues. It guides the AI to trace bugs backward through the call stack to identify the original trigger, saving significant time and reducing frustration when facing hard-to-spot problems.

Core Features & Use Cases

  • Multi-tool Integration: Leverages a suite of tools and subagents including rg, fd, kg (knowledge graph), git-jj, outbox, and oracle for comprehensive context gathering and strategic advice.
  • Iterative Debugging Process: Follows a clear cycle of understanding the issue, fetching shallow context, reviewing available tools, generating debugging ideas, tracing, and verifying fixes.
  • Advanced Reasoning: Utilizes outbox for high-level debugging strategies and oracle for advanced reasoning about complex issues, ensuring effective decision-making.

Quick Start

The 'tree city picker' does nothing when I click the input. Help me debug this issue by gathering related code modules and asking for debugging ideas.

Frequently Asked Questions about debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a bug backward through call stacks to find the root cause?

Root-cause analysis traces bugs backward through call stacks by identifying the original trigger point. This Skill systematically backtracks through code execution paths, using context search and code history to isolate where the issue originated rather than where symptoms appear.

Can I debug complex issues across multiple files or repositories?

Yes. This Skill handles multi-file and multi-repo debugging by integrating knowledge graphs, fast repository context gathering, and git history tools to support iterative root-cause analysis across distributed codebases with vague symptoms.

What's the best way to approach troubleshooting when I don't know where the problem started?

Systematic debugging follows a structured cycle: understand the issue, gather shallow context, review available tools, generate debugging ideas, trace execution paths, and verify fixes. This approach reduces time spent on elusive, hard-to-spot problems.

How do I integrate code analysis tools into my debugging workflow?

This Skill integrates `rg` for fast searching, `kg` for knowledge graph context, `git-jj` for code history, and collaborative tools to gather comprehensive context and propose root-cause fixes within a unified debugging cycle.

Do I need advanced reasoning to debug issues in complex codebases?

Advanced reasoning tools help tackle complex issues by leveraging high-level debugging strategies and sophisticated analysis. This Skill applies oracle-level reasoning to decide which debugging paths are most effective for multi-layer problems.