Menu
Track down a bug methodically instead of guessing (use when the user reports something is broken / throwing / not working)
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
Sort a messy Downloads folder into per-type subfolders (use when the user says their Downloads is a mess / wants it organized)
Stage changes and write a clean conventional commit message (use when the user wants to commit their work / says "commit this")
Read recent email and sort it into what actually needs a reply (use when the user asks what's in their inbox / to triage their email)
Scaffold a fresh Python project — folder, virtualenv, .gitignore, README, git init (use when the user wants to start a new Python project)
Move screenshots into YYYY-MM dated folders so the desktop/screenshots folder stops drowning (use when screenshots are piling up)
Research a topic across several sources and write a cited brief (use when the user asks you to research / "look into" / summarize a topic from the web)
| name | debug-it |
| description | Track down a bug methodically instead of guessing (use when the user reports something is broken / throwing / not working) |
| version | 1.0.0 |
| author | 0pen-sourcer |
| tools | ["run_command","read_file","grep_search","edit_file"] |
Find the ROOT cause before changing anything. Reproduce, isolate, fix, verify — no shotgun edits.
run_command to run it and capture the real error text / stack trace. If you cannot reproduce it, say so and ask for the exact steps — do not guess.grep_search for the error message or the failing function to find the code, then read_file around that line — enough context to understand it, not just the one line.edit_file that addresses it — not a band-aid around the symptom.