Menu
Debug errors using logs and stack traces. Use when the user shares an error message, crash log, or runtime issue to fix.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate commit messages for staged git changes. Use when the user asks to generate a commit message or wants help writing commit messages.
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Explain errors without editing files. Use when the user wants to understand an error or crash but not immediately fix it.
Analyze code for logical errors, runtime bugs, and edge cases. Use when the user wants a code review, asks to find bugs, or wants to check code correctness.
Image manipulation via a bundled script, resizing, rotation, flipping, cropping, padding, format conversion (JPEG/PNG/WebP/TIFF/HEIC), transparency operations (remove/replace/extract/blend), grayscale conversion, auto-cropping borders, and file size optimization.
Convert documents to Markdown. PDFs go through the LlamaParse API (best quality, costs credits, tier selectable) or a local PyMuPDF engine (free, offline, no API key); other formats (DOCX, PPTX, XLSX, HTML, EPUB) are converted locally with markitdown.
| name | debug-issue |
| description | Debug errors using logs and stack traces. Use when the user shares an error message, crash log, or runtime issue to fix. |
When debugging an issue, follow every step in order:
Check input: If no error message was provided, stop and ask for the exact error text or log. If the failing file is not available, ask for it. Do not guess at code you have not seen.
Locate the failure: Quote the single most informative line of the stack trace (deepest frame inside the user's own code, not library code) and name the file and line it points to.
State the root cause: One or two sentences explaining WHY the error occurs, the mechanism, not a restatement of the error text.
Propose the fix: Show the smallest code change that fixes the root cause, as a before/after snippet. Wait for user confirmation before editing any file.
Scope limits:
Output template (use these exact sections):
## Root cause
<mechanism, 1-2 sentences>
## Evidence
<quoted stack-trace line or log line, with file:line>
## Fix
<before/after code snippet>
## Why this works
<1-2 sentences>
Guardrails: never claim certainty you do not have, if two causes are plausible, present both and say which is more likely and why; never edit files before the user confirms; never say "should work", explain why it works.