Event in (Cloud pipelines are the event-driven half of the automation surface. Something happens in GitHub (an issue is filed, a CI run fails, a PR is opened), the reusable workflows inissues.opened,workflow_run,pull_request). PR out. Every step runs on GitHub-hosted runners or RunsOn spot, attributable to the AI-bot App identity.
JacobPEvans/ai-workflows react, and the result lands as a draft PR or a commit on an existing PR — signed by JacobPEvans-claude[bot] and ready for review.
The cron-driven sibling — work that runs on a schedule rather than in response to an event — is documented under Scheduled routines.
How they fit
| Trigger | Reusable workflow | Outcome |
|---|---|---|
issues.opened (label: agentic-implement) | issue-resolver.yml | Draft PR implementing the issue |
workflow_run on CI, conclusion: failure | ci-fix.yml | Fix commit pushed back to the failing PR |
pull_request opened or synchronize | code-simplifier.yml, final-pr-review.yml | Review comments + an auto-merge nudge when ready |
gh-aw action SHA stale (Mon/Thu schedule) | gh-aw-pin-refresh.yml | PR refreshing pinned action SHAs |
Where to go next
ai-workflows
Reusable workflows, GH-AW imports, the consumer-caller shape, auth + signing.
Scheduled routines
The cron-driven sibling. Org-wide, no per-repo wiring.
Issue to PR pipeline
The end-to-end flow on
JacobPEvans/docs, step by step.Git signing
How AI-authored commits land verified under the
JacobPEvans-claude[bot] identity.