Skip to content

ci: autotriage new pull requests with a Claude Code routine - #537

Merged
barjin merged 5 commits into
masterfrom
feat/pr-claude-routine
Sep 2, 2026
Merged

ci: autotriage new pull requests with a Claude Code routine#537
barjin merged 5 commits into
masterfrom
feat/pr-claude-routine

Conversation

@barjin

@barjin barjin commented Sep 2, 2026

Copy link
Copy Markdown
Member

Fires the routine once per PR (on open, or on ready-for-review for drafts) and can be triggered manually with a PR URL; needs an AUTOREVIEW_CLAUDE_CODE_TOKEN secret.

@github-actions github-actions Bot added this to the 148th sprint - Tooling team milestone Sep 2, 2026
@github-actions github-actions Bot added the t-tooling Issues with this label are in the ownership of the tooling team. label Sep 2, 2026
@barjin barjin changed the title ci: fire the Claude Code review routine on new pull requests ci: autotriage new pull requests with a Claude Code routine Sep 2, 2026
@barjin
barjin requested a review from Pijukatel September 2, 2026 09:37
-H "anthropic-version: 2023-06-01" \
-H "anthropic-beta: experimental-cc-routine-2026-04-01" \
-H "Content-Type: application/json" \
-d "$(jq -n --arg url "$PR_URL" '{ text: "Review the pull request at \($url)" }')"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does this simple prompt work for you? i've started with this back in the day, and it was full of invalid reports, that's where the staff review skill was born, its first iteration just added a verification step and that itself dropped most of the invalid findings, making the review much more valuable. maybe things changed nowadays (and running the staff review for token cost likely wont be cheap).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a much more comprehensive prompt in the Claude Routine itself; this one is just appended to the routine one (basically just passing the PR URL).

Image

At this point, I'm just experimenting here. The routine contains pretty much the same prompt I would run locally anyway. No aspiration to have no human loop here yet.

@barjin barjin left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scale matches scope (33-line additive CI workflow, single file, no breaking changes). Couldn't find any problems.


Generated by Claude Code

@barjin barjin changed the title ci: autotriage new pull requests with a Claude Code routine ci: autotriage new pull requests and issues with Claude Code routines Sep 2, 2026
@barjin barjin changed the title ci: autotriage new pull requests and issues with Claude Code routines ci: autotriage new pull requests with a Claude Code routine Sep 2, 2026

@Pijukatel Pijukatel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's see how it behaves and tune it based on it.
(You can easily turn off the routine if it misbehaves)

@barjin
barjin merged commit 28bd730 into master Sep 2, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants