Skip to main content
Event in (issues.opened, workflow_run, pull_request). PR out. Every step runs on GitHub-hosted runners or RunsOn spot, attributable to the AI-bot App identity.
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 in 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

The full caller catalog and the post-merge dispatch chain live on the ai-workflows page.

​
Where to go next

ai-workflows

Reusable workflows, pinned prompts, 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.