J Debug
Description
--- 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: "<bug-description-or-failing-test>" 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
Installation
Installs to ~/.claude/commands/jlaws-dotfiles-j-debug.md
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.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Spec Kit
💫 Toolkit to help you get started with Spec-Driven Development
Testing Webapp Testing
Test local web applications using Playwright for UI verification and debugging
Testing #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/ever
Testing Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing sol
Testing Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test sui
Testing gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release M
Testing