pudo-handoff
Write the PUDO session handoff (.pudo/session.md) so another session, tool or teammate can continue the work. Use when the user…
Skill, Debugging, SRE, Bug Fixing
Claude Code
$ npx -y skills add DongDuong2001/pudo-code-system --skill debug --agent claude-code
Codex
$ npx skills add DongDuong2001/pudo-code-system --skill debug -a codex -y
Cursor
$ npx skills add DongDuong2001/pudo-code-system --skill debug -a cursor -y
Gemini CLI
$ npx skills add DongDuong2001/pudo-code-system --skill debug -a gemini-cli -y
GitHub Copilot
$ npx skills add DongDuong2001/pudo-code-system --skill debug -a github-copilot -y
OpenCode
$ npx skills add DongDuong2001/pudo-code-system --skill debug -a opencode -y
Windsurf
$ npx skills add DongDuong2001/pudo-code-system --skill debug -a windsurf -y
> Skill, Debugging, SRE, Bug Fixing
Use this prompt when you are facing a bug, error trace, or unexpected behavior. This skill forces the AI to act as a troubleshooter, analyzing root causes systematically rather than just guessing solutions.
Adopt the persona of a Senior Site Reliability Engineer (SRE) / Troubleshooter. I am encountering a bug and need your help to diagnose and fix it systematically.
Error Message / Stack Trace:
{{error_message}}
Expected vs Actual Behavior:
{{behavior_description}}
Relevant Code Context:
{{context_code}}
Please follow this debugging methodology:
1. **Root Cause Analysis:** Analyze the error and the code to explain exactly *why* this error is happening at a technical level.
2. **Hypotheses:** Provide 1-2 probable reasons if the root cause isn't 100% obvious from the snippet.
3. **The Fix:** Provide the exact code changes required to resolve the issue.
4. **Regression Prevention:** Briefly explain how this fix ensures the bug won't happen again (e.g., edge case handling).
Do not guess blindly. If you need more information to diagnose the issue accurately, ask for it.**Input:**
Adopt the persona of a Senior Site Reliability Engineer (SRE) / Troubleshooter. I am encountering a bug and need your help to diagnose and fix it systematically.
Error Message / Stack Trace:
TypeError: Cannot read properties of undefined (reading 'map') at UserList.tsx:24
Expected vs Actual Behavior:
I expected the list of users to render, but instead the app crashes when the API takes too long to respond.
Relevant Code Context:
const UserList = ({ users }) => {
return <div>{users.map(u => <span key={u.id}>{u.name}</span>)}</div>
}
Please follow this debugging methodology:
[...rest of prompt...]Write the PUDO session handoff (.pudo/session.md) so another session, tool or teammate can continue the work. Use when the user…
PUDO Plan phase: turn a request into a short plan card (goal, scope, out of scope, success criteria, risks, steps) before any…
PUDO Optimize gate: review the current diff against the plan before calling work done: correctness, edge cases, tests, scope…
PUDO workflow: Plan -> Understand -> Develop -> Optimize. Use on any non-trivial coding task (features, bug fixes, refactors,…
- [ ] **API Design:** Define RESTful endpoints, path parameters, and query parameters. - [ ] **Data Validation:** Plan Pydantic…
- [ ] **Framework Selection:** Choose web framework (Axum, Actix-web) based on performance vs. ecosystem needs. - [ ] **Crate…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.