Agentic Workflows

Hud's runtime data isn't only for your IDE — you can feed it to coding agents (Claude, Codex, Cursor) so they reason about real production behavior when they review PRs, clean up code, or report on health. This page is the entry point to a library of ready-to-run agentic workflows that do exactly that.

Every recipe is open source and lives in the hud-agentic-workflows-recipes repository — the source of truth for the prompts, runner templates, and fully worked examples referenced below. Pick a use case, pick a runner, copy the files.

📘
How it works
Each workflow is a use case (what the agent does) running on a runner (where it executes). Any use case works on any runner. Every workflow authenticates to Hud with a single HUD_MCP_KEY secret passed to npx -y hud-mcp@v2.

The recipes

Four use-case prompts ship today. Each one is runner-agnostic — it uses env vars and generic instructions so you can pair it with any runner.

Recipe	What it does
Blast radius	Scores the production blast radius of a PR (0–100) by mapping changed code to affected functions and endpoints, then writes a ranked Markdown report.
Weekly report	Multi-phase weekly deep-insights report on production health — proposes fixes, annotates contributors, and optionally opens a self-heal PR, then posts to Slack.
Dead-code cleanup	Finds functions with zero production invocations over a lookback window and opens a PR removing them (with optional Jira ticket).
Rollback check	Compares current vs. previous release health per version and returns a structured verdict: ROLLBACK / INVESTIGATE / WARN / CLEAN.

The matrix

Each cell pairs a recipe with a runner. See example cells are fully worked and install-ready; mix & match cells you wire together yourself (see How to mix & match).

	GitHub Actions (Claude · Codex)	gh-aw	Cursor	Claude routine
Blast radius	see example	mix & match	mix & match	mix & match
Weekly report	mix & match	see example	mix & match	mix & match
Dead-code cleanup	mix & match	mix & match	see example	mix & match
Rollback check	mix & match	mix & match	mix & match	see example

see example — a fully worked, install-ready combo. Click through to the install guide.
mix & match — grab the prompt + runner template and wire them together (see below).

Pick your path

I know which use case and runner I want. Find the cell in the matrix. If it's see example, follow that example's install README. If it's mix & match, see How to mix & match.

I have a use case but need to pick a runner. Compare the Runners table below, then choose your cell.

I want to build something custom. Pick a runner from runner-templates/ and write your own prompt — or start from one in task-recipes/prompts/.

Runners

Runner	Integration	What you do	Best for
GitHub Actions	Copy files	Copy `.github/` files to your repo and set secrets. Two templates: Claude CLI or Codex CLI.	PR-triggered workflows, cron jobs, teams already on GH Actions
gh-aw	Copy files	Copy `.github/workflows/*.md`, run `gh aw compile`, set secrets	Same triggers as GH Actions, with a markdown+YAML agent format
Cursor	Copy + UI	Copy `AGENTS.md` to your repo, create an automation in the Cursor dashboard, add MCP servers, set secrets	Teams using Cursor; manual or scheduled triggers
Claude routine	Copy file or register	Skill: copy `.claude/skills/` to your repo. Scheduled: register the prompt via an MCP tool call	On-demand (skill) or continuous cron monitoring (scheduled)

How to mix & match

When the matrix says mix & match, you're pairing a prompt with a runner template:

Grab the prompt from task-recipes/prompts/.
Grab the runner template from runner-templates/.
Follow the runner template's README for where to place the prompt and what to configure.
Check the prompt's env-var table for any variables you need to wire up in the runner config.

Repo structure

runner-templates/         Runner skeletons. How it runs.
  github-actions-claude/  GitHub Actions + Claude Code CLI
  github-actions-codex/   GitHub Actions + Codex CLI
  gh-aw/                  Copy .github/workflows/*.md to repo
  cursor/                 Copy AGENTS.md to repo + UI setup
  claude-routine/
    skill/                Copy .claude/skills/ to repo
    scheduled-remote/     Register via MCP tool call (no files)

task-recipes/
  prompts/                Use-case prompts. What it does.
    blast-radius.md
    weekly-report/
    dead-code-cleanup.md
    rollback-check.md
  team-splitting/         Cross-cutting patterns for scoping by team.

full-examples/            Fully worked combos (runner + prompt + install README).
  blast-radius-github-actions/
  weekly-report-gh-aw/
  dead-code-cleanup-cursor/
  rollback-check-claude-routine/

docs/                     Auth guides, secrets reference, screenshots.

Auth

Every workflow authenticates to Hud with a single HUD_MCP_KEY secret passed to npx -y hud-mcp@v2.

Get the key: hud.io → Settings → MCP keys.

For Anthropic vs. Bedrock model auth, see docs/auth.md in the recipes repo.

Contributing

These recipes are community-extensible. To add a new use case or runner pairing, see CONTRIBUTING.md. The repo is MIT-licensed.