Skip to Content
ChainsKinds

Opinionated templates. Each has a When, allowed Then steps, and locked fields. Cite the ID in proposals and future MCP calls.

Available · later means the template is in the product’s create flow, but is not part of the recommended first enablement. It does not mean “not shipped.”

IDNameWhenThen (default / typical)Availability
pull_request_slack_live_cardPR Slack live cardSelected PR eventsOne channel card, updated in place; optional 12h reminderRecommended
pull_request_review_slaReview SLAreview_requestedReviewer DM at 4h; owner DM at 24h by defaultRecommended, after identity readiness
production_rollout_changelogProduction changelogSuccessful deployment in production/prodWait ≤300s for association; announce PRs or commitRecommended, deploy-producing repo
scheduled_reportScheduled reportCalendarRun saved report, then announce summary/CSVRecommended
personal_digestPersonal digestMember’s weekday local timePrivate Overview › For me snapshotSelf-serve. Hidden from create/list; not admin-toggleable
urgent_pr_needs_reviewerUrgent PR needs reviewerUrgent linked ticket + no reviewerRequest review, notify, escalate, blockAvailable · later. Default includes block_merge
reviewer_at_capacityReviewer at capacityRequested reviewer above thresholdReroute review, notifyAvailable · later
breaking_schema_changeBreaking schema changeSchema change without compatibility evidenceComment, DM schema owner, blockAvailable · later. Default includes block_merge
cicd_change_without_owner_reviewCI/CD change without owner reviewWorkflow / infrastructure path changeRequest CI owner, blockAvailable · later. Default includes block_merge
rule_fired_actRule violated → actNamed rule finding opensComment, fail check, announceAvailable · later. Default includes fail_check
stale_pull_requestStale pull requestNo activity during the configured business-hours waitNudge author, then team leadAvailable · later
deployment_review_waitingDeployment review waitingProduction approval still waitingNudge approvers, then ownerAvailable · later
failed_workflow_default_branchFailed workflow on default branchCI red on the default branchAnnounce; optionally create deduplicated Linear issueAvailable · later
large_pr_without_testsLarge PR without testsSize threshold + no matching test pathComment + needs-tests labelAvailable · later
issue_live_cardIssue live cardSelected issue eventsOne Slack card, updated in placeAvailable · later
deployment_review_live_cardDeployment-review live cardEnvironment review eventsOne Slack cardAvailable · later
review_feedback_follow_upReview feedback → follow-upChanges requested/actionable comment, author quietNudge author, then escalateAvailable · later
bot_approval_needs_humanBot approval needs humanApproval exists but no human approvalRequest/nudge human reviewAvailable · later
repository_without_ownerRepository without ownerGoverned repo loses its individual ownerNotify an admin channelAvailable · later
from_scratchFrom scratchAny supported eventSupported custom When → ThenAvailable · later. Shown separately after opinionated templates

Safety notes

  • Defaults containing block_merge or fail_check are real GitHub-writing steps. Review and adjust them; dry-run is required before enablement.
  • personal_digest is created only by its owner from Overview › Needs attention › Customize.
  • breaking_schema_change evaluates one repository’s schema evidence. Named cross-repository counterpart enforcement is a separate not-generally-available control, not a hidden default in this template.
  • “From scratch” can only use events, conditions, waits, actions, and destinations exposed by the catalog. It is not permission to invent a new trigger.
Last updated on
When then ThenDry-run