11 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

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

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

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 turns an incident timeline and the last week of commit history into a blameless postmortem — summary, impact, timeline, root causes, contributing factors, what went well, and action items with owners and due dates — written to postmortem/POSTMORTEM.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

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