$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 and scan the whole org. They pick up loose ends
that nothing else watches for: stale READMEs, missing .gitignore rules,
unresolved review threads, weekly summaries.
The event-driven sibling is documented under Cloud pipelines.
What runs on a schedule
The routines live indryvist/claude-code-routines
as a small set of prompt files. Each one runs on its own schedule inside Anthropic’s cloud-hosted
Claude Code sandbox. It discovers repos via gh search, does its work by calling the gh
command-line tool, 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 all live as composable home-manager modules. The result is reproducible
across machines and rolls 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 issue triage, routing, and review.
Issue to PR pipeline
Where routines fit relative to the rest of the issue-to-PR flow.