Menu
Create a minimal reproduction for a bug. Use when the user asks to create a repro.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Render a document, a diagram, or a report as HTML for human visualisation.
Use when writing prose meant to read by humans: PR descriptions, docs, blog drafts, emails, design memos
Guidelines on creating issues on GitHub
Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: 'premortem this', 'premortem my', 'run a premortem', 'what could kill this', 'future-proof this', 'stress test this plan', 'what am i missing here', 'find the blind spots'. STRONG TRIGGERS: 'what could go wrong', 'am i missing anything', 'poke holes in this', 'where will this break', 'devil's advocate this'. Do NOT trigger on simple feedback requests, or factual questions. DO trigger when someone has a plan or commitment where the cost of being wrong is high.
Schedule a prompt to fire back at yourself at a future time or on a recurring cron pattern. Use when the user says "remind me", "every N minutes/hours/days", "at HH:MM tomorrow", "check X periodically", or otherwise asks for any time-based action. Triggered by the `schedule` tool plus the `/schedule` command for listing and deletion.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get roasted on their design, or mentions "brainstorm".
| name | repro |
| description | Create a minimal reproduction for a bug. Use when the user asks to create a repro. |
| user-invocable | true |
| argument-hint | Please provide a link or reference to the issue and any relevant context or steps to reproduce. |
If the user hasn't given you any context, start by asking them for a link or reference to the issue and any relevant context or steps to reproduce.
From that link or reference, gather as much information as you can about the bug, such as:
A minimal reproduction is a small, self-contained codebase that demonstrates the bug in question. It should be as simple as possible while still reproducing the issue.
Tips:
pnpm create next-app --example reproduction-template <repro-name> to quickly scaffold a minimal app.