Time in (cron). Org-wide scan out. One configuration, every repo under $GH_OWNER, no per-repo wiring.
Scheduled routines are the cron-driven half of the automation surface. The event-triggered cloud pipelines react to things that already happened in a single repo; the routines run on a schedule, scan the whole org, and pick up loose ends — stale READMEs, missing .gitignore rules, unresolved review threads, weekly summaries — that nothing else watches for.
The event-driven sibling is documented under Cloud pipelines.
What runs on a schedule
The routines live inJacobPEvans/claude-code-routines as a small set of prompt files. Each one runs inside Anthropic’s cloud-hosted Claude Code sandbox on its own schedule, discovers repos via gh search, does its work using gh CLI calls, and reports results to Slack.
There is no per-repo wiring. Add a repo to the org and the routines pick it up on the next scheduled run.
How the install is managed
The local Claude Code that runs these routines is configured declaratively in Nix viadryvist/nix-claude-code — plugins, marketplaces, skills, hooks, MCP servers, and permissions as composable home-manager modules. Reproducible across machines, rolled back with one command.
Where to go next
claude-code-routines
The routine catalog, schedules, and operator setup.
nix-claude-code
Declarative Claude Code via home-manager modules. How the routine host stays reproducible.
Cloud pipelines
The event-triggered sibling that handles per-repo issues and CI failures.
Issue to PR pipeline
Where routines fit relative to the rest of the issue-to-PR flow.