Add general PR review workflow#76
Merged
Merged
Conversation
9954a63 to
824e8f2
Compare
ggreer
approved these changes
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Non-connector repositories need the shared PR review ruleset without requiring baton-admin to manage repository Actions variables. The current single entry point defaults to connector review, which is right for connector repos but forces a per-repo override for SDKs and other adjacent repos.
What this changes
Adds a central general-pr-review required workflow that hardcodes the general prompt profile. Refactors the PR review action so prompts are composed from a shared base prompt plus built-in mixins: connector repos still use the existing pr-review workflow and receive the connector mixin by default, while general review uses the base prompt only. Trusted repo-local ci-review skills remain supported for project-specific rules.