exec-debugging
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded when a task involves fixing bugs, tracing errors, or diagnosing failures.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 7
When implementing a task that requires debugging, follow this strict Chain-of-Thought process BEFORE writing any fix:
- Distinctive: line 12
Minimal Fix: Do not rewrite the entire function.
- Distinctive: line 16
Only after completing these 6 steps should you apply the fix.
≈ “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
Debugging Execution Strategy
When implementing a task that requires debugging, follow this strict Chain-of-Thought process BEFORE writing any fix:
- Reproduce & Isolate: What is the exact state or sequence of events that triggers the bug? Which specific file/function is the boundary of the error?
- Formulate Hypotheses: State the 2-3 most likely root causes based on the error trace or behavior.
- Gather Evidence: What logs, variable states, or code paths confirm which hypothesis is correct?
- Minimal Fix: Do not rewrite the entire function. Propose the absolute minimum change required to resolve the issue.
- Verify Root Cause: Explain why this fix addresses the root cause and not just the symptom.
- Safety Check: Could this minimal fix break other parts of the system? (e.g., downstream consumers of this function).
Only after completing these 6 steps should you apply the fix.
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.