Skip to content

docs(perps-review-pr): accept a branch or commit range as the review request - #260

Merged
abretonc7s merged 1 commit into
mainfrom
perps-review-branch-input
Nov 18, 2026
Merged

abretonc7s merged 1 commit into
mainfrom
perps-review-branch-input

Conversation

@abretonc7s

Copy link
Copy Markdown
Contributor

Explanation

perps-review-pr already supports reviews without a PR: the verdict step in each repos/<repo>.md says "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.md is regenerated from the Perps rules at the same revision (398decc), so no rule content changes. --check passes.

Examples:

/mms-perps-review-pr review branch my-feature against origin/main
/mms-perps-review-pr review commits abc123..def456

Checklist

  • Skill-only change; no CHANGELOG entry

@abretonc7s
abretonc7s requested a review from a team as a code owner November 17, 2026 23:53
@abretonc7s
abretonc7s enabled auto-merge (squash) November 18, 2026 00:03
@abretonc7s
abretonc7s merged commit d1f8a4c into main Nov 18, 2026
29 checks passed
@abretonc7s
abretonc7s deleted the perps-review-branch-input branch November 18, 2026 00:20
@andrepimenta andrepimenta mentioned this pull request Nov 18, 2026
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants