5 workflows

runcastle

A single Claude Code agent that finds the least-tested modules in your repo, writes focused unit tests for them one module at a time, and verifies the suite stays green after every batch — stopping once it hits your coverage target.

runcastle

A single Claude Code agent brings your dependencies up to date in safe batches — patches, then minors, then one major at a time — fixing any breakage it introduces, gated by a hard build + test check every round until everything is current and green.

runcastle

An Opus planner triages your open `bug`-labelled GitHub issues into independent fixes, then a swarm of Sonnet fixers fans out — one per issue, each on its own branch — to reproduce, root-cause, patch, and test the bug in parallel.

runcastle

A single Claude Code agent reads your offer and ideal-customer notes and writes a complete 5-touch cold email sequence — subject-line options, tight bodies, send timing, one clear CTA per email, and personalization tokens ready to merge at send time.

runcastle

A single Claude Code agent reads your repository — a shell-expanded file map seeds it, and it can install and run the project — then writes and incrementally commits a real `docs/` set: a getting-started guide, an architecture overview, and per-module reference pages.