Debug session
Skill lubochka/xiigen-general-skills/codex/skills/debug-session
Open-source AI agent skills for safer Claude, Codex and Cursor coding workflows
npx -y skills add lubochka/xiigen-general-skills --skill debug-sessionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Package debugging work so another agent or human can resume it. Use for longer debugging tasks or handoffs.
SKILL.md
0.8 KB, 145 tokens by cl100k_base, as published. Nobody here has run it
Debug Session
Purpose
Package debugging work so another agent or human can resume it.
When to Use
Use for longer debugging tasks or handoffs.
Inputs
Goal, environment, repro, observations, attempted fixes, blockers.
Steps
- State the debug goal.
- Record repro steps and environment.
- Track attempts and results.
- End with conclusion, blocker, or next step.
Gates
The session is understandable without hidden context.
Evidence
Debug session notes, checked files, and command results.
Anti-Patterns
Leaving only "it fails" without repro or observations.
Related
systematic-debugging, session-output-contract
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most debug triage skills give in 145 tokens
Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07
- Investigate root cause before proposing any fixin 102 of 839, across 67 files
- Read error messages completelyin 89 of 839, across 49 files
- Create a failing test case before fixingin 84 of 839, across 46 files
- Reproduce the issue consistentlyin 82 of 839, across 41 files
- Change one variable at a timein 82 of 839, across 42 files
- Check recent changesin 74 of 839, across 36 files
- Write the regression test before fixingin 74 of 839, across 40 files
- Fix the root cause not the symptomin 60 of 839, across 45 files
- Implement a single fix at a timein 59 of 839, across 20 files
- Trace data flow backward to the sourcein 50 of 839, across 20 files
- Remove all debug instrumentationin 49 of 839, across 13 files
- Form a single hypothesisin 48 of 839, across 18 files
Said here and by no other author read
- state the debug goal
- record repro steps and environment
- track attempts and results
- end with conclusion, blocker, or next step
- make the session understandable without hidden context
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.