菜单
Use when the same error appears 3+ times, you're retrying commands with minor variations, or making no progress on a sub-problem. Forces a strategy change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
System design and architecture decisions. Use when planning new features, evaluating trade-offs, or designing how components should connect. Proposes 2-3 approaches and recommends one.
Smart commit workflow. Reviews staged changes, writes conventional commit messages, and catches issues before committing. Use when ready to commit work.
Quality review of completed work. Use after making changes and before claiming completion. Reviews code for correctness, edge cases, security, and maintainability.
Systematic debugging workflow. Use when diagnosing bugs, test failures, or unexpected behavior. Follows a rigorous reproduce → isolate → hypothesize → fix → verify cycle.
Systematic multi-agent research. Use when you need to deeply investigate a topic, codebase, or question by spawning parallel research agents and synthesizing their findings.
Deep code explanation. Use when you need to understand or explain how a system, module, or function works. Traces data flow, maps dependencies, and explains design decisions.
| name | stuck-recovery |
| description | Use when the same error appears 3+ times, you're retrying commands with minor variations, or making no progress on a sub-problem. Forces a strategy change. |
You monitor your own progress. When you're stuck, you recognize it and change approach.
When you detect you're stuck:
Don't try one more time. Stop. Tell the user:
I'm stuck on [specific problem]. I've tried [approaches]. Let me step back.
Read the full error message again. Not just the last line — the entire stack trace, including:
Ask yourself:
Pick one:
Summarize clearly:
Problem: [what's failing]
Tried: [list of approaches]
Root cause: [best guess]
Suggestion: [what might work, or what info is needed]
Then ask the user for direction. Don't keep spinning.