Skip to main content
Open issue. Don’t open the dashboard. Come back in five minutes to a draft PR ready for your eyes.
The pipeline on this repo, JacobPEvans/docs, uses six thin caller files in .github/workflows/ that delegate to reusable workflows in JacobPEvans/ai-workflows. Each caller is 10–30 lines; the AI work all lives in the upstream reusable workflow.

​
What runs, in order

​
How the six callers connect

The hub is the consumer repo; each caller is a one-shot wrapper around an upstream reusable workflow. They run independently when their trigger fires.

​
What each caller actually contains

A caller is the minimum YAML to declare a trigger, set permissions, and call the upstream:
Two patterns are slightly larger:
  • ci-fix.yml passes a repo_context and ci_structure describing what the repo is and what CI runs, so the AI knows what to fix.
  • post-merge-docs-review.yml uses the Post-Merge Dispatch Pattern — a two-job file because push events aren’t supported by claude-code-action@v1, so the caller re-dispatches as workflow_dispatch.

​
Secrets the pipeline needs

Distributed automatically by secrets-sync when a repo is added to the _github_app_repos and _all_repos anchors in secrets-config.yml: Per Git signing, every AI workflow mints a JacobPEvans-claude installation token immediately before calling claude-code-action@v1, then hands it in as github_token with use_commit_signing: true. Commits land web-flow-signed and attributed to the bot.

​
Rate and safety guards

The reusable workflows enforce conservative defaults so a runaway loop can’t burn cloud spend:
  • issue-resolver.yml — max_attempts: 1 per issue, daily_limit: 5 per repo, excluded_labels: "type:security,type:feature,type:breaking,size:l,size:xl" won’t touch
  • ci-fix.yml — daily_run_limit: 5 per repo, max 2 fix attempts per PR
  • All workflows — fork PRs blocked by if: guards, branch protection enforces the final merge gate

​
The pieces this doesn’t include

The cloud pipeline gets a PR to draft + reviewed. It does NOT:
  • Mark the PR ready for merge — that’s a human decision
  • Click the merge button — never automated
  • Override branch protection or required reviewers
  • Touch repos outside the current org boundary
For the local iteration loop on a PR you’re editing yourself, see /ship and /finalize-pr.

​
Where to go next

ai-workflows

Reusable workflows, pinned catalog prompts, event-triggered and scheduled.

claude-code-routines

The cron half — six routines that scan the org and pick up loose ends.

ai-workflows getting started

Caller templates and the live workflow catalog.

Authentication

AI_TOKEN, provider routing, and model variables.