6 workflows

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 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 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

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

Fetches a single target page and audits its on-page SEO — title, meta, headings, canonical, Open Graph, structured data, alt text, internal links, word count — then writes a prioritized, fix-by-fix action list you can hand to a developer.

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.