Agents
Built around the part everyone gets wrong: when a key leaks you rotate it first — it's compromised the second it hits a remote, and bots scan public pushes within seconds. Scans staged changes, the working tree, and git history for provider key shapes, private keys, committed .env/credential files, and hardcoded creds — tuned for signal over noise so placeholders and $ENV refs don't cry wolf — then walks rotate → purge-from-history → move-to-env → add-a-pre-commit-hook, in the right order.
Built around the parts of API integration everyone skips until 3am: token refresh, pagination to the last page, 429 rate-limit handling, retries with backoff + jitter, idempotency keys so a retry doesn't double-charge, timeouts, and typed error handling. It reads the API's own docs, matches your stack, keeps keys in env, and produces a client that survives the network blinking — not a naive fetch that falls over the first time the API throttles you.
Built around one rule learned the hard way: never make a git mess worse. Before anything risky it snapshots a backup ref, then guides you through the real recovery toolkit — reflog rescue for "lost" commits, interactive rebase, cherry-pick, safe revert vs hard reset, fixing "committed to the wrong branch," and bisect to find where a bug crept in — flagging at each step which moves are reversible and which are destructive. Safety-first git surgery for when things go sideways.