xiduzo/wtf / skills/wtf.hotfix
wtf.hotfix
VerifiedThis skill should be used when something is broken in production and needs an immediate fix that bypasses the normal Epic→Feature→Trace planning flow — for example "production is down", "hotfix needed", "critical bug in prod", "emergency fix for
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.5 KB |
| evals/evals.json | config | 4.4 KB |
| evals/fixtures/narrow-fix.json | config | 1.1 KB |
| evals/fixtures/pr-body-completeness.json | config | 1.1 KB |
| evals/fixtures/scope-gate-fires.json | config | 1.4 KB |
evals/fixtures/narrow-fix.json
View on GitHub{
"_note": "Narrow, well-scoped hotfix: floating-point truncation in settlement calculation. Used by eval 1 to test branch naming and slug derivation (step 4 only).",
"bug": {
"number": 88,
"title": "Bug: Settlement amount rounds incorrectly for amounts above 10,000",
"labels": [{"name": "bug"}],
"body": "## What is broken?\n\nMerchants receiving settlement payouts for amounts above £10,000 are consistently underpaid by £0.01. The issue has been traced to `calculateSettlementAmount()` in the settlement service, which uses JavaScript floating-point division.\n\n## User impact\n\nRevenue impact: all merchants processing settlements above £10,000. Approximately 200 settlements per day are affected, each short by £0.01.\n\n## Steps to reproduce\n\n1. Create a settlement for £10,000.01\n2. Observe `calculateSettlementAmount()` returns £10,000.00\n\n## Expected behaviour\n\nSettlement amount should match the exact pence value, with no floating-point rounding error.\n\n## Actual behaviour\n\nSettlement amount is £0.01 less than expected for any amount above £10,000."
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |