Post @claude review comment on the current PR and ask what's next. Use on `/pr-review` to trigger the GitHub Actions review workflow.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add bravros/bravros --skill pr-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pr Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bravros-pr-review)More formats (shields.io, HTML) on the badges page.
---
name: pr-review
core: true
description: Post @claude review comment on the current PR and ask what's next. Use on `/pr-review` to trigger the GitHub Actions review workflow.
---
# pr-review
Read [briefing.md](references/briefing.md) on demand for detailed context and instructions.
INTENT: post ONE verbatim `@claude` comment; the GitHub Action reviews asynchronously (~2–5 min)
and posts back to the PR. This skill never reviews, never polls, never merges.
## Core Steps
1. **Determine PR Number**: Use `$ARGUMENTS` if numeric, else `gh pr view --json number -q .number`. If none, STOP ("create one with /pr first").
2. **Branch Sync**: If behind base branch, rebase and `git push --force-with-lease` first. Handle conflicts according to mode (ask in interactive / note & proceed in autonomous).
3. **Post Comment**: Send verbatim `@claude` comment with visible sentinel verdict lines (`BRAVROS-VERDICT: approved` / `BRAVROS-VERDICT: changes-requested`).
- **NEVER write a bare `#N` for a review-finding number.** GitHub autolinks `#N` in every
issue/PR body — it cannot be disabled, and it also writes a cross-reference event onto that
issue's timeline, so referring to "finding #3" silently spams an unrelated old issue and
renders as its title mid-sentence. Write `finding 3`, or wrap it in backticks. Reserve bare
`#N` for a genuine issue/PR you mean to link. Same rule applies to the PR body.
- `bravros police` enforces this comment at tool-call time: the body must start with the exact
canonical opening and end with the exact `Required:` block (extra instructions may go in
between); `--body-file`/`-F` is refused outright. A blocked attempt gets the canonical
template back in the block message — retry with that verbatim.
4. **Verdict & Stamp Rules**:
- `BRAVROS-VERDICT:` is authoritative. Prose is report-only.
- `bravros pr-review "$PR" --write-stamp` is the single source of truth for writing `.planning/.review-stamp-<PR>.json`.
5. **After Posting**:
- Autonomous: Print `STATUS: review-triggered. NEXT: wait for stamp`.
- Interactive: Advise user to run `/address-pr` when complete.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!