Claude Code Routines

claude-code-routines

Home of `issue-solver`: a scheduled GitHub Actions workflow that picks one Linear task and opens one ready-for-review pull request that closes it.

The seven cloud routines this repo used to run were retired on 2026-08-06 with the hosting substrate they ran on. [`docs/RETIREMENT.md`](docs/RETIREMENT.md) records why, where each prompt's content went, and which trigger ids must never be reused. [DESIGN.md](DESIGN.md) keeps the origin story and the lessons.

The one routine

Routine	Schedule (UTC)	Purpose
issue-solver	0 0,12 * * *	Solve one Linear task, open one PR

It runs in GitHub Actions on a GitHub App installation token. It never touched the cloud-routine substrate, which is why it kept working through the outage that ended the others. `workflow_dispatch` is enabled, so you can run it on demand without waiting for the cron.

How it fits together

dryvist/ai-llm-prompts            the prompt body lives here
  automation/issue-solver.md
        |
        |  pinned as a submodule
        v
vendor/ai-llm-prompts             this repo's pinned copy
        |
        |  scripts/render-routine.sh issue-solver
        v
.rendered-issue-solver.md         frontmatter stripped, includes expanded
        |
        v
.github/workflows/issue-solver.yml

This repo owns the consumer half only — the schedule, the token, the model, and the allowed-tools list. The prompt text belongs to the catalog. Changing what the routine *says* is a catalog change; changing when or how it *runs* is a change here.

Files that matter

• routines/registry.yaml — the pinned catalog commit and the prompt filename.
• scripts/render-routine.sh — strips OKF frontmatter, expands markers.
• .github/workflows/issue-solver.yml — the scheduled run.
• .github/workflows/render-check.yml — proves the render still works