Reusable Workflows
Callers reference a workflow at @main, so a change here reaches every repo as soon as it merges.
A repo calls one as a job in its own workflow:
jobs:
my-job:
uses: birdygrey/.github/.github/workflows/<workflow>.yml@main
with:
<input>: <value>
secrets:
<SECRET>: ${{ secrets.<SECRET> }}
Caller examples and full input tables are in the README.
All of them need the org secrets ANTHROPIC_API_KEY and either BIRDY_BOT_PAT (for GitHub) or BIRDY_BOT_SLACK_TOKEN (for Slack), and act as Birdy Bot.
Repo guidelinesβ
The Claude workflows take an optional repo_guidelines input. Callers fill it from a rule file in their own repo, so each repo can add its own review or description criteria:
- A small first job checks out only
.claude/rules/<name>.mdand outputs its contents. - The main job passes that output as
repo_guidelines.
| Workflow | Rule file |
|---|---|
| PR review | .claude/rules/pr-review.md |
| PR description | .claude/rules/pr-description.md |
Claude PR reviewβ
Reviews a pull request and posts inline comments with a severity, plus a summary review.
caller_workflow_filenameandbot_usernamelet it skip a pull request it has already reviewed or is reviewing.- A failed review fails the check.
Claude PR descriptionβ
Writes the description of a pull request when it's opened. It takes only repo_guidelines and the two secrets. A failure doesn't fail the check.
Release notesβ
Writes notes for a release with Claude, updates the GitHub release body, and posts a summary to one or more Slack channels.
- Each repo keeps its own voice and format in
.github/release-notes-prompt.md; the workflow supplies the commits. include_pr_context: trueadds the merged pull requests' descriptions, which gives better notes.- If the model answers
NO_CONSUMER_FACING_CHANGES, nothing is posted and the GitHub release is left as is. Prompts tell it when to say that. - Repos that don't tag (like the claude repo) pass
previous_refto set the start of the range.
Claude QAβ
Runs after a deploy: reads the release's pull requests, tests the environment with Playwright, and replies with a QA report under the release's Slack message. It takes the environment URL, the release notes and tags, and the Slack thread to reply in. No repo calls it yet.
Web Vitals actionβ
A composite action, not a workflow. It runs Lighthouse against qa-host for each page in scopes and compares the results with Google's Core Web Vitals thresholds. No repo uses it yet.