Review PR
Review a PR diff and emit machine-readable feedback to review.json, never posting to GitHub directly
- What
- Review a PR diff and emit machine-readable feedback to review.json, never posting to GitHub directly
- Cost
- Free
- Needs
- an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); local PR artifacts (annotated diff, PR description) supplied by your workflow
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the first PR-review skill in the catalog. A deterministic review workflow for teams that automate review: from local artifacts (pr_diff.txt, pr_description.txt) it produces structured verdicts in review.json (severity labels, diff-line annotations with [OLD:n]/[NEW:n] prefixes — line numbers are the only source of truth) instead of posting to GitHub directly, so a pipeline can publish them. Priorities: correctness, security, error handling, meaningful performance; comment and test quality are first-class, not optional nits. When spec context exists, it validates implementation-vs-spec via a companion script. Distinct from warpdotdev-create-pr (this lot): that one creates PRs, this one reviews them. References sibling skills not yet indexed (review-pr-local, security-review-pr, check-impl-against-spec) as future candidates. By @warpdotdev, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); local PR artifacts (annotated diff, PR description) supplied by your workflow Install "Review PR" for me. Review a PR diff and emit machine-readable feedback to review.json, never posting to GitHub directly Repository: https://github.com/warpdotdev/common-skills/blob/main/.agents/skills/review-pr/SKILL.md 1. Fetch the SKILL.md file for the warpdotdev-review-pr skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "warpdotdev-review-pr". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.