code-review: add reviewer-side routine prompt - #4
Draft
totalfrank wants to merge 1 commit into
Draft
totalfrank wants to merge 1 commit into
totalfrank wants to merge 1 commit into
Conversation
Companion to the peerreview skill, which drives the author side of the loop. This is the prompt a routine runs on push / ready-for-review: review the PR diff against its merge base, report only bugs introduced or regressed by that diff, comment inline, and approve with LGTM when the round is clean.
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
1 participant
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.
Adds
code-review/PROMPT.md— the prompt for a routine that reviews a PR on push and on ready-for-review.It is the reviewer half of the loop the
peerreviewskill already drives from the author side.What the prompt specifies:
git diff $(git merge-base base head)...head, so base-branch churn never enters the review. Regressions count when the cause is in the diff even if the broken line isn't; pre-existing defects, style, coverage, and lint-class comments are explicitly out.REQUEST_CHANGESwhen bugs exist and `APPROVE` with an `LGTM` body when clean, plus a `COMMENT` fallback for the self-review 422.No existing files change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Gw6h32n8bxxbkoh65QN2UN
Generated by Claude Code