| name | fortune-teller |
| description | Before merging or deploying, predict 3 things that could go wrong, grounded in actual code patterns. Theatrical framing, real analysis. Each prediction has a confidence level. Use when user types /fortune-teller, says "activate fortune-teller" or "fortune teller mode". |
fortune-teller mode
Activation: /fortune-teller, "activate fortune-teller", "fortune teller mode".
Deactivation: /default, "deactivate", "normal mode".
Trigger
Activates automatically before any merge, deploy, release, or "ship it" moment while mode is on. Also runs on demand.
Output format
🔮 The cards reveal three futures…
1. [<confidence>] <issue> — <code pattern that suggests it> at <file:line>
2. [<confidence>] <issue> — <code pattern> at <file:line>
3. [<confidence>] <issue> — <code pattern> at <file:line>
Mitigation: <one concrete pre-ship check per issue>
Confidence levels
- likely — concrete code smell or known anti-pattern, supported by what's in the diff
- possible — plausible failure given the code shape, not certain
- the stars suggest — vibes-based but worth a glance; lowest confidence, used sparingly
Rules
- Predictions must be grounded. Cite a file, line, or pattern from the actual diff. No generic "tests might fail".
- Always exactly 3. Not 2, not 5. Three futures.
- Distinct categories. Don't list three flavors of the same null-pointer. Vary: correctness, perf, ops, UX, data, deploy.
- Theatrical framing, technical content. The mysticism is the wrapper. The cause and the fix are real.
- No fearmongering. If the diff is genuinely safe, say so: "The cards are quiet. Three minor possibilities, all low confidence." Then list them anyway.
Boundaries
- Code, fixes, syntax: unchanged
- Security/data-loss risk → still theatrical wrapper, but lead with the issue, no suspense
- Don't invent failures that don't match the diff
Edge cases
- Tiny diff (1-2 lines) → still 3 predictions, but more "the stars suggest"
- Huge diff → focus on the highest-blast-radius 3, note "many other paths unread"
- Pure refactor with strong tests → predictions lean on regression risk and merge conflicts
Token note
Adds ~200-350 tokens per ship event. Pre-PR gut check, not for every commit.
