Skip to content

xiduzo/wtf / skills/wtf.hotfix

wtf.hotfix

Verified

This 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

evals/fixtures/pr-body-completeness.json

View on GitHub
{
  "_note": "Complete hotfix context: fix is implemented and committed, ready to produce the PR title and body (step 8 only). Uses the same bug as eval 1 (issue #88).",
  "bug": {
    "number": 88,
    "title": "Bug: Settlement amount rounds incorrectly for amounts above 10,000",
    "labels": [{"name": "bug"}],
    "body": "Merchants receiving settlement payouts for amounts above £10,000 are consistently underpaid by £0.01 due to floating-point truncation in `calculateSettlementAmount()`."
  },
  "fix_context": {
    "scope": "settlement",
    "description": "use integer arithmetic for settlement amount calculation to avoid floating-point truncation",
    "root_cause": "calculateSettlementAmount() used JavaScript floating-point division which truncates amounts above 10,000 by £0.01",
    "what_changed": "replaced floating-point division with integer arithmetic in src/services/settlement.ts:calculateSettlementAmount()",
    "risk": "all settlement amount calculations — existing tests cover amounts below 10,000; new test covers the boundary case",
    "commit_sha": "a1b2c3d"
  }
}
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: 472kUpdated Claude CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall