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

runcastle

Fans out an analyst agent per competitor to fetch and dissect each rival's site — pricing, positioning, messaging, gaps — then a strategist synthesizes the teardowns into a single positioning brief with sharp, defensible angles for your product.

runcastle

A mixed-provider copy pipeline: a Claude Code writer turns your product brief into full AIDA-structured landing page copy, then a Codex editor cuts fluff, makes claims concrete, and tightens headlines on the same warm branch, looping until it ships.

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

A single Claude Code agent reads your product and segment notes, then produces a defensible TAM/SAM/SOM estimate using both top-down and bottom-up methods — every assumption stated, a sensitivity table, and honest caveats — written to research/market-sizing.md.

runcastle

A single Claude Code agent reads raw meeting notes and turns every actionable item into a clean, ready-to-file issue draft — one markdown file per action with title, context, acceptance criteria, and a suggested owner and label — plus an INDEX.md summary table.

runcastle

Reads a links.md list of URLs, fetches each one inside the sandbox, and has a Claude Code agent write a ready-to-send newsletter digest — a tight 2–3 sentence summary of every link, why it matters to your readers, and the source link, all assembled into a single markdown issue.

runcastle

Turn a single topic into a publish-ready blog post through three sequential Claude Code passes on one warm branch: an Opus strategist outlines the angle and keywords, a Sonnet writer drafts the full post, and an Opus editor tightens the prose and optimises it for search.

runcastle

A Claude Code agent performs a refactor, a hard `npm test` gate proves nothing broke, then a Codex reviewer adversarially audits the change on the same warm branch — hunting regressions, weak tests, and shortcuts — fixing and looping until it approves.

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

A single Claude Code agent reads a metrics.csv, computes week-over-week deltas, and writes an executive narrative — what moved, why it likely moved, what to watch, and one recommended action — alongside a compact metrics table, to reports/weekly.md.

runcastle

A single Claude Code agent reads the commits since your last tag, groups them into Added/Changed/Fixed/Security by user-facing intent, and writes a clean CHANGELOG.md entry plus a friendly RELEASE_NOTES.md — turning raw git history into release-ready notes in one pass.

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

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.