simple-debug
Skill1 starsChanged 43 days agoMITView on GitHub
Find serious bugs before ship, or trace a reported bug to its root cause. Use when the user asks to debug, hunt bugs, or find why something breaks. Reports only, does not fix unless asked.
In this repository15 other files it gives its agents.
- simple-cantoneseSkill
- simple-checkSkill
- simple-chineseSkill
- simple-cloudflareSkill
- simple-code-reviewSkill
- simple-commitSkill
- simple-full-refactorSkill
- simple-launchSkill
- simple-orchestratorSkill
- simple-readmeSkill
- simple-refactorSkill
- simple-releaseSkill
- simple-restructureSkill
- simple-supabaseSkill
- simple-text-cleanupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Read the code paths involved before claiming a bug.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Simple Debug
Scan for high impact issues only. Scope is the whole codebase unless the user names files, a feature, or a symptom. If a symptom is given, trace it to the root cause first.
Look for problems that
- Break core logic or core workflows
- Cause crashes or runtime failures
- Corrupt data or produce invalid states
- Block user actions or ruin the user experience
- Introduce security risks or unsafe behavior
Ignore style issues, harmless edge cases, and personal preferences.
Rules
- Read the code paths involved before claiming a bug. Trace real inputs through the logic.
- Report only what you can explain with a concrete failure scenario. Drop guesses.
- Separate real bugs from engineering tradeoffs. Mention a tradeoff briefly, never as a bug.
- Report only. Do not change code unless the user asks.
Output
For each bug:
file:line- What breaks, and the input or state that triggers it
- A one line suggested fix
End with a verdict: safe to ship, or not, and the blockers. If nothing serious is found, say so plainly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.