debug
Skill3 starsChanged 27 days agoMITView on GitHub
Build a failing loop before you diagnose a hard bug, flaky test, regression or slowdown, with read-only Grafana, ArgoCD or Kubernetes evidence. Use when a report says only "broken".
192 other projects use a version of this.
Adopted by
Most recently taken up by
- PeanutGT/NutsSkillstheir own version, first seen Nov 8, 2026
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- Firzus/agent-skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- microsoft/veronatheir own version, first seen Nov 8, 2026
Used with
Projects with it also use add-discord, add-slack and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
- MicrosoftSkill
add-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
- +10 more from microsoft
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- anthropics/knowledge-work-plugins★ 35ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- openai/symphony★ 27ksame name
- FalkorDB/FalkorDB★ 10ksame name
- NVIDIA/TensorRT-Model-Optimizer★ 5.6ksame name
- NVIDIA/Model-Optimizer★ 5.6ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- adrSkill
- api-contract-syncSkill
- architecture-advisorSkill
- ci-triageSkill
- compassSkill
- delivery-digestSkill
- design-taste-skillsSkill
- grillSkill
- harness-improveSkill
- harness-loopSkill
- impact-analysisSkill
- native-mobile-skillsSkill
- plugin-authorSkill
- pr-flowSkill
- project-memorySkill
- remaining-workSkill
- reviewSkill
- slide-deckSkill
- spec-flowSkill
- task-flowSkill
- ui-conformanceSkill
- working-style-skillsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
9
Distinctive
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 11
No theory before the loop.
- Distinctive: line 15
Stop at the first rung that catches the bug.
- Distinctive: line 43
Remove inputs until each remaining part is needed.
- Distinctive: line 45
Keep the loop as the regression check.
- Distinctive: line 50
When read-only Grafana, ArgoCD or Kubernetes MCP servers are configured, use them for evidence:
- Distinctive: line 56
Use them read-only. Never change a dashboard, a sync, or a cluster resource from this skill.
- Distinctive: line 57
Never read a Secret. If a server is not configured, say so.
- Distinctive: line 58
If a server is not configured, say so.
- Distinctive: line 76
Stop. Ask for the missing artifact: logs, a HAR file, a fixture, environment access, or permission for temporary instrumentation.
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
debug
No theory before the loop. First build one command that catches the exact symptom.
Loop ladder
Stop at the first rung that catches the bug.
- An existing focused test.
- A new smallest regression test.
- A CLI or script with fixture input.
- An HTTP request against a running service.
- A Playwright or browser script for a UI bug.
- A replay of a captured trace.
- A small harness around one function or module.
- A stress loop for a flaky bug.
Tighten the loop
The loop must be:
- Specific: it asserts the symptom that the user reported, not "does not crash".
- Fast: seconds when possible.
- Deterministic: the same verdict each time, or a high reproduction rate for a flake.
- Runnable by an agent: no manual clicks, unless a written script wraps them.
A loop that asserts an absence needs a floor. A blank page has no forbidden class, and a process that never started writes no forbidden log line. Assert that the subject exists, then assert the absence. Wait for the floor, do not sample it once. Collect the survivors in a list and assert that the list is empty, so a failure names each survivor. A static search proves only that a literal is absent from the source.
Work
- Name the loop command. Run it once and see it fail.
- Remove inputs until each remaining part is needed.
- Change one thing at a time.
- Keep the loop as the regression check.
- Report the command, the failing result, the passing result and the remaining uncertainty.
Evidence from the running system
When read-only Grafana, ArgoCD or Kubernetes MCP servers are configured, use them for evidence:
- Grafana: the logs, metrics and traces of the failing window.
- ArgoCD: the sync state and the deployed revision of the app.
- Kubernetes: pod status, events and logs.
Use them read-only. Never change a dashboard, a sync, or a cluster resource from this skill. Never read a Secret. If a server is not configured, say so. Do not ask the user to add write access.
A claim of change needs a control
A screenshot, log excerpt, benchmark or query result is weak evidence. A boring cause may give the same result. Capture the control in the same session.
| The claim | The control |
| This screen differs from the rest of the app | A screen that agrees, on the same device |
| The fix removed the error | The earlier log window, with the error present |
| This is faster now | The old build, on the same machine |
| The flag turns the feature off | The same screenshot with the flag on |
Say in one sentence what the control rules out.
If no loop is possible
Stop. Ask for the missing artifact: logs, a HAR file, a fixture, environment access, or permission for temporary instrumentation.
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.