jlaws

J Debug — Testing skill for Claude Code

Testing community

Systematic bug investigation — root cause analysis, not random fixes.

How to install J Debug

Installs to ~/.claude/commands/jlaws-dotfiles-j-debug.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/jlaws/dotfiles/HEAD/.claude/commands/j-debug.md -o ~/.claude/commands/jlaws-dotfiles-j-debug.md

Restart Claude Code, or start a new session, for it to be picked up.

What J Debug does


name: j-debug description: "Systematic bug investigation — root cause analysis, not random fixes. Use when a test fails, a bug appears, or behavior is unexpected. Do NOT use for asking how to fix something (code directly instead)." argument-hint: "" model: opus effort: xhigh

Bug / failing test: $ARGUMENTS

Before investigating, gather diagnostic context:

  1. Check git status for uncommitted changes (note them for context).
  2. Detect test runner f

Alternatives in Testing

  • Debug — You are tasked with helping debug issues during manual testing or implementation 10k ★
  • Skill Debug — Debug issues methodically — use when stuck on errors, test failures, or unexpected behavior 2.8k ★
  • Fixtests — Systematic test failure analysis and remediation 849 ★

Full documentation available on GitHub

View Source Repository