coding-debugger

Coding Debugger

Never solve the same bug twice

AI-assisted debugging memory for coding agents. It learns from past incidents, classifies similar failures, and supports deep root-cause workflows for hard fixes.

Features

Core

• Incident Tracking — Store debugging incidents with symptoms, root causes, fixes, and verification
• Verdict System — Results classified as KNOWN_FIX, LIKELY_MATCH, WEAK_SIGNAL, or NO_MATCH
• Progressive Depth — One-liner results (~40 tokens each), drill into full details on demand
• Keyword Indexing — Inverted index for O(log n) retrieval instead of scanning every file
• Context Engine — Auto-injects memory stats into sessions, file-aware editing hints
• Outcome Tracking — Records whether suggested fixes actually worked
• Quality Scoring — Automatic completeness scoring (0-100%)
• Pattern Extraction — Auto-extracts reusable patterns after 3+ similar incidents
• Enhanced Search — Multi-strategy: exact, tag, fuzzy (Jaro-Winkler), category
• Audit Trail Mining — Recovers incidents from .claude/audit files
• Benchmark Suite — 6-dimension scoring system to measure system quality

Integrations

• Parallel Assessment — Multi-domain analysis (database, frontend, API, performance)
• Trace Ingestion — OpenTelemetry, Sentry, LangChain, Browser adapters
• Parallel Retrieval — Concurrent memory search for faster results
• Plugin Marketplace — Install directly via Claude Code plugin system

Storage

• Dual Modes — Local (.claude/memory/ per project) or Shared (~/.claude-code-debugger/ global)
• Tiered Storage — Index (O(1) lookup), JSONL (fast search), individual files (on-demand)
• Auto-archival — Old incidents archived after 200 active or 180 days
• Context Compression — Token-optimized output for LLM injection

Installation

Via Plugin Marketplace

# Add the marketplace
/plugin marketplace add tyroneross/claude-code-debugger

# Install the plugin
/plugin install coding-debugger@claude-code-debugger

Via npm (includes CLI and automatic slash command setup)

# npm
npm install @tyroneross/claude-code-debugger

# pnpm
pnpm add @tyroneross/claude-code-debugger

# yarn
yarn add @tyroneross/claude-code-debugger

Global Installation (for CLI access anywhere)

# npm
npm install -g @tyroneross/claude-code-debugger

# pnpm
pnpm add -g @tyroneross/claude-code-debugger

# yarn
yarn global add @tyroneross/claude-code-debugger

The package name stays @tyroneross/claude-code-debugger for compatibility. The preferred CLI binary is coding-debugger; claude-code-debugger remains as an alias.

Troubleshooting Installation

pnpm store mismatch error: If you see ERR_PNPM_UNEXPECTED_STORE, your project has a local .pnpm-store directory. Fix with:

rm -rf .pnpm-store node_modules
pnpm install

npm/pnpm conflict: If your project uses pnpm (has pnpm-lock.yaml), always use pnpm add instead of npm install.

Quick Start

Slash Commands (Claude Code)

After installation, these slash commands are automatically available in Claude Code:

Command	Description
/debugger "symptom"	Search past bugs for similar issues before debugging
/debugger	Show recent bugs and pick one to debug
/debugger-detail <ID>	Drill into a specific incident or pattern
/debugger-status	Show memory statistics
/debugger-scan	Scan recent sessions for debugging incidents
/assess "symptom"	Run parallel domain assessment (database, frontend, API, performance)

Examples:

/debugger "API returns 500 on login"
→ One-liner matches with verdicts (KNOWN_FIX, LIKELY_MATCH, etc.)
→ Use /debugger-detail <ID> to drill into any match

/debugger-detail INC_API_20260215_143022_a1b2
→ Full incident details: root cause, fix, verification, files changed

/debugger-status
→ "5 incidents stored, 2 patterns, 12 KB used"

/debugger-scan
→ Scans recent sessions for debugging incidents

CLI Usage

# Check current configuration
claude-code-debugger config

# Show memory statistics
claude-code-debugger status

# Search memory before debugging
claude-code-debugger debug "Search filters not working"

# Search for specific incidents
claude-code-debugger search "react hooks"

# Drill into a specific incident or pattern
claude-code-debugger detail INC_REACT_20260215_001

# Record whether a suggested fix worked
claude-code-debugger outcome INC_REACT_20260215_001 worked

# Suggest patterns to extract
claude-code-debugger patterns

# Extract and store patterns
claude-code-debugger patterns --extract

# Mine audit trail for missed incidents
claude-code-debugger mine --days 30

# Store mined incidents
claude-code-debugger mine --days 30 --store

# Rebuild keyword index (after manual edits)
claude-code-debugger rebuild-index