troubleshooting-workflow
Skill0 starsChanged 7 months agoMITView on GitHub
Use when a concrete failure, regression, or confusing broken state must be debugged systematically and captured in `docs/troubleshooting`. Trigger for failing tests, broken builds, runtime errors, user-reported incidents, or environment-specific failures.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- decision-recordingSkill
- harness-bootstrapSkill
- issue-driven-workflowSkill
- planning-workflowSkill
- review-workflowSkill
- spec-writingSkill
- subagent-workflowSkill
- technical-learning-noteSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Treat failures as reusable incident history, not just something fixed in passing.
- Distinctive: line 12
Stop adding unrelated work until the failure is understood.
- Very specific: line 17
Add a troubleshooting note in docs/troubleshooting/ when the incident would help another Codex user.
≈ “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
Troubleshooting Workflow
Treat failures as reusable incident history, not just something fixed in passing.
Default flow
- Stop adding unrelated work until the failure is understood.
- Preserve the symptom, reproduction steps, and affected paths.
- Narrow the fault before applying a fix.
- Record the actual root cause, not only the visible symptom.
- Validate the fix and note what proved it.
- Add a troubleshooting note in
docs/troubleshooting/when the incident would help another Codex user. - Decide whether the incident should also create a guardrail or decision record.
Good fit
- broken user-facing behavior
- failing tests or builds
- regressions after a recent change
- bugs that required more than one guess to understand
Avoid for
- already-understood failures with no reusable learning
- speculative cleanup not tied to a concrete incident
Resources
- See
references/incident-checklist.mdfor the core incident fields.
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.