7 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 reads the diff and commit history of your branch against its base, then writes a complete, reviewer-ready PR_DESCRIPTION.md — summary, what changed, why, testing, risk, and a reviewer checklist — grounded entirely in the real diff.

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.

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

Fans out a searcher per sub-question to fetch and note public web sources, then an Opus synthesizer writes a fully cited report, then a Codex fact-checker adversarially verifies every claim against the notes and loops until the report holds up.

runcastle

Reads a sources.md list of papers, fetches each one, and builds a structured literature review — per-source summary of question, method, finding, and limitation — then synthesizes the themes, disagreements, and open gaps across the whole set.

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.