pr-review · diff

v1.0.0 to v1.0.0

2 added, 2 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: pr-review
version: 1.0.0
description: GitHub Actions PR review bot with Greptile parity — confidence 0-5, risk gates, checks annotations, and fix loop. Install via setup-vskills.
---
# PR Review
Polished GitHub-Actions review bot. Copy the templates into any repo with `setup-vskills` or `node standalone/pr-review/scripts/copy.mjs`.
## What it installs
- `.github/workflows/pr-review.yml` — diff-aware review, status checks, collapsible summary (PR Summary, Confidence Score 0-5, Issue Table, Sequence Diagram, Comments Outside Diff)
- `.github/workflows/pr-fix.yml` — fix comment trigger, one commit per comment, max 3 loops then `needs-human`
- `.vskills/review.yml` — all toggles: when to review, file-change limit (100), filters, strictness Low/Med/High, comment header, status checks (requiredConfidence 0-5), auto-approve (maximumRisk Low/Med/High/Critical)
## Triggers
- Trusted `pull_request_target: [opened, synchronize, reopened, ready_for_review]`; checks out the PR head as data and executes no PR-controlled code. Collaborators can rerun with `@vskills review`.
- - `issue_comment: created` when the comment starts with `/fix`. Same-repo collaborators only. Forks cannot push.
- - After a verified `/fix` push, the fix job dispatches this workflow because `GITHUB_TOKEN` commits do not fire `pull_request_target`.
+ - `issue_comment: created` when the comment line begins with the fix command. Same-repo collaborators only. Forks cannot push.
+ - After a verified fix-on-comment push, the fix job dispatches this workflow because `GITHUB_TOKEN` commits do not fire `pull_request_target`.
## BYOK model
OpenRouter via `OPENROUTER_API_KEY` and `vars.REVIEW_MODEL` / `vars.REVIEW_API_BASE`. Without a key the workflow still posts a limited deterministic review (conflict detection and credential-pattern scan on added lines). It does not run PR-controlled `npm` scripts.
## CONTEXT-aware
If the consumer repo has `CONTEXT/glossary.md` or `architecture.md`, the review job injects them (8k token cap) before chunking hunks (80 lines) and running ripgrep context.
## Verification
```
node --test 'test/pr-review-*.test.js'
```
Templates carry `<!-- vskills-pr-review -->` for idempotent upserts.