Repository navigation
docs(perps-review-pr): accept a branch or commit range as the review request - #260
Merged
Merged
Conversation
abretonc7s
enabled auto-merge (squash)
November 18, 2026 00:03
geositta
approved these changes
Nov 18, 2026
Merged
cursor Bot
pushed a commit
that referenced
this pull request
Nov 18, 2026
Folds the post-branch merges into the curated 0.4.0 changelog per review: #258/#262 (mm-harness 0.96.33) into the recipe entry, #260/#261 into the perps-review-pr entry, #264 rule pack and #231 CV lint checklist as new entries, drops the inaccurate analytics-move BREAKING entry, and links Co-authored-by: George Marshall <georgewrmarshall@users.noreply.github.com> #207 on the tsc-blindspots entry.
5 of 11 tasks
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
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.
Explanation
perps-review-pralready supports reviews without a PR: the verdict step in eachrepos/<repo>.mdsays "for a branch-only review, use an empty comments array". But the checklist never says a branch or commit range is a valid request, or which base to use, so people assume it needs a PR URL.The "Record the review context" row now says the request may be a PR URL, a branch or a commit range, and that a branch is reviewed against its merge-base with the default branch. The row lives in
materialize-review.mjs;skill.mdis regenerated from the Perps rules at the same revision (398decc), so no rule content changes.--checkpasses.Examples:
Checklist