code-debug
Troubleshoot a problem by researching the error and proposing a minimal fix.
Process
- Identify the error message, log, or failure symptom from the user's request or context
- Research the error:
- Search the codebase for related code paths and error handling
- Check documentation for the libraries/frameworks involved (use WebSearch/WebFetch)
- Search the web for known issues, fixes, or similar error reports
- Analyze the root cause based on research findings
- Propose a minimal fix
Output
- Likely cause
- Evidence (links or doc references)
- Fix
- Verify
More from sirn/dotfiles
code-commit
Commit current changes using jj. Analyzes changes, suggests commit messages following repository conventions, proposes splits if needed, and creates commits. Use ONLY when user explicitly asks to commit changes or create commits.
18gemini-reference
Reference for calling the Gemini CLI agent from other agents. ALWAYS read BEFORE invoking Gemini to ensure correct JSON protocol, session management, and subtask delegation patterns.
18code-quality
Run comprehensive quality checks by orchestrating review, verification, testing, and linting. Use when user asks to check code quality, run full checks, or verify code health.
18context7
Retrieve up-to-date documentation context for libraries using the Context7 API. Use when needing current library documentation (React, Python stdlib, Rust, etc.) BEFORE implementing or writing code.
17code-setup-project
Sets up project development environment (wrapper scripts and/or Nix flake). Use when user wants to set up a development environment, create wrapper scripts, or add a Nix flake.
17code-generate-document
Generate documentation, docstrings, or ADRs. Use when asked to document code or create decision records.
17