Automation

How an issue becomes a merged PR with minimal human touch: ai-workflows in the cloud, claude-code-routines on cron, claude-code-plugins on the laptop.

File an issue. Walk away. Come back to a draft PR with green CI, AI review, and one human merge click left.

This is the issue → mergeable PR pipeline. Three repos collaborate: ai-workflows runs on GitHub Actions per consumer repo, claude-code-routines runs on Anthropic’s cloud cron, claude-code-plugins is the local Claude Code escape hatch.

The end-to-end shape

A human files the issue and clicks merge. Everything in between runs without supervision.

The three layers

Layer	Where it lives	When it runs	What it owns
ai-workflows	GitHub Actions (per consumer repo)	Event-triggered (issues, PRs, CI failures)	Triage, draft PR creation, CI auto-fix, final review gate, project routing
claude-code-routines	Anthropic cloud cron	Scheduled (cron 2×/day to weekly)	Org-wide maintenance: daily polish, issue solver, sentinel audit, weekly scorecard
claude-code-plugins	Your laptop	Interactive (/ship from any Claude Code session)	The local escape hatch — finalize a PR you’re iterating on

The six moving parts

Issue → PR pipeline

The eight-step cloud flow on a target repo. Which trigger fires which file, who reviews, what gates merge.

ai-workflows

The 16 reusable workflows behind the cloud pipeline. Event-triggered and scheduled.

claude-code-routines

Six cron-scheduled Claude routines. Org-wide maintenance, no per-repo wiring.

/ship + /finalize-pr

The local skill that closes the loop on a PR you’re iterating on. Phases, exit modes, the known reliability gaps.

CodeQL resolution

Why CodeQL is fixed separately from CI checks, and how /resolve-codeql plugs in.

Shaping issues

The /shape-issues skill that turns rough ideas into well-scoped issues the resolver can act on.

Source repos

ai-workflows · claude-code-routines · claude-code-plugins. The 30-second pitch lives at AI pipeline; this Automation section is the mechanics.