Developer productivity plugins by RossLabs
npx claudepluginhub tyroneross/claude-code-debuggerDebugging memory — learn from past bugs with verdict-based retrieval, pattern extraction, and parallel domain assessment. Never solve the same bug twice.
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage
Curated collection of 141 specialized Claude Code subagents organized into 10 focused categories
Never solve the same bug twice
A debugging memory system for Claude Code that automatically learns from past incidents and suggests solutions based on similar problems you've already solved.
.claude/audit files.claude/memory/ per project) or Shared (~/.claude-code-debugger/ global)# Add the marketplace
/plugin marketplace add tyroneross/claude-code-debugger
# Install the plugin
/plugin install claude-code-debugger@claude-code-debugger
# npm
npm install @tyroneross/claude-code-debugger
# pnpm
pnpm add @tyroneross/claude-code-debugger
# yarn
yarn add @tyroneross/claude-code-debugger
# npm
npm install -g @tyroneross/claude-code-debugger
# pnpm
pnpm add -g @tyroneross/claude-code-debugger
# yarn
yarn global add @tyroneross/claude-code-debugger
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.
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
# 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