メニュー
Triggers on error messages, stack traces, "this is broken", unexpected output, or debugging requests. Focuses on root cause analysis, ranked hypotheses, and targeted fixes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Proactively log small friction points, flaky commands, failed tool calls, or setup gotchas to `PAPERCUTS.md` using `yarn papercut`. Trigger on any friction encountered during work or when the user invokes `/papercut`.
Turn real work the user has actually done into a Reddit post for technical, developer-centric, or AI-related subreddits. Use whenever the user says "write me a Reddit post", "help me post on Reddit", "turn this into a Reddit post", "share this on Reddit", or anything similar — and also proactively suggest this skill when the user just finished something post-worthy (a benchmark, a workflow they figured out, a bug/incident diagnosis, a tool/framework comparison, a meaningful failure). The skill REFUSES to generate posts from nothing — it requires real work, real numbers, real experience as the input. Karma-farming generic listicles are explicitly out of scope.
Activates an interactive interview mode to resolve design decisions, clarify vague requirements, and align on a plan. Trigger on "/align", "align", "interview me", "let's align", or when the user has an ambiguous plan and needs to be questioned to solidify it.
Run a user-given shell command directly and return raw output, no commentary.
Execution mode. Trigger on "go ahead", "do it", "execute", "implement", "make the changes", or any approval to act. Stop planning, start building.
Multi-model analysis and synthesis using OpenCode CLI — replicates OpenRouter Fusion style workflows locally. Runs multiple LLMs in parallel, judges their outputs, and produces a single synthesized response. Trigger whenever the user wants to run a task against multiple models, compare model outputs, get a consensus answer, or says things like "fusion run", "multi-model", "run all models", "synthesize model outputs", or "parallel agents". Also trigger when the user wants to reduce hallucinations by cross-checking multiple LLMs, or when high-stakes tasks need more than one model's perspective.
| name | debug-issue |
| description | Triggers on error messages, stack traces, "this is broken", unexpected output, or debugging requests. Focuses on root cause analysis, ranked hypotheses, and targeted fixes. |
Be a systematic debugger. Understand the root cause before fixing. Think like a senior engineer doing a post-mortem.
If missing, ask one targeted question to clarify:
List 2-3 possible causes (logic, state, async, env, API, side-effects).
H1 [Most likely]: <cause> → Why: <reasoning> → Check: <verification>
If the error/behavior is ambiguous, silently search the web for known bugs or similar reports.
Suggest a fast verification method (e.g., a specific log, repro step, or test).
