pr-review · datawithbaraa — Claude Code skill: what it does, how to install
The pr-review Claude Code skill reviews a file, diff, or branch before a change is merged. It checks the work against project standards and produces an HTML report.
MIT ★ 106 updated 2026-11-06
/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills
/plugin install data-engineering@data-with-baraaWhat pr-review does
The skill examines one change in a set sequence: scope, security, data correctness, tests, contracts, portability, duplication, architecture, performance, documentation, and style. Each finding includes its risk, file and line, the relevant project rule, and a suggested fix.
The result is a single HTML page with an approve or changes-requested verdict; high-risk findings come first. If the author rejects a finding, it stays in the report with the stated reason. The skill reads the change, standards, tests, and consumer data contracts. It does not edit code, push changes, or merge a branch.
What it helps with
- spot exposed secrets and access-control issues
- check data types and outputs against consumer contracts
- find missing tests and uncovered edge cases
- catch machine-specific paths and duplicated code
- present findings and a verdict in one HTML report
Example prompts for the agent
- Review branch
feature/new-modelagainst the project standards before merge. - Check the current diff and report findings with suggested fixes.
- Review
models/orders.sqland return the verdict as an HTML report.
How to install pr-review
1Plugin marketplace
/plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills/plugin install data-engineering@data-with-baraaThis installs the whole data-engineering plugin with all its skills
2Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill pr-review -a claude-code3Manually: put the files in place
~/.claude/skills/pr-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-review/
1Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill pr-review -a codex2Manually: put the files in place
.agents/skills/pr-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill pr-review -a cursor2Manually: put the files in place
.cursor/skills/pr-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install DataWithBaraa/claude-code-data-engineering-skills skills/pr-review2Manually: put the files in place
.github/skills/pr-review/SKILL.md1Skills CLI (Vercel)
npx skills add DataWithBaraa/claude-code-data-engineering-skills --skill pr-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/DataWithBaraa/claude-code-data-engineering-skills --path skills/pr-reviewManually: put the files in place
.devin/skills/pr-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pr-review
How do I install pr-review in Claude Code?
Run /plugin marketplace add DataWithBaraa/claude-code-data-engineering-skills, then run /plugin install data-engineering@data-with-baraa.
What does pr-review do?
It checks a file, current diff, or branch against project standards and produces an HTML report with a verdict, risks, and proposed fixes.
Does pr-review change code or merge branches?
No. It writes a report only; it does not edit the change, push it, or merge it.
Source text
SKILL.md · MIT
--- name: pr-review description: Use before a pull request or another change goes in, on a file, the current diff or a branch, to review it pass by pass against the project's own standards, with pushback. argument-hint: "[branch, diff or file]" --- # Pull request review The job: review one change in fixed passes, in this order, and report every finding with its fix. It never edits. Input: a file, the current diff, or a branch before its merge. ## Steps 1. Scope the change: the files, the lines and the purpose of the change. 2. Security: secrets in the code, access rights, personal data that reaches the consumers. 3. Correctness: data types, money, the numbers the change produces, and the same result on a rerun or a backfill. 4. Tests: the change comes with tests, they cover the edge cases, and they pass. 5. Contract: the grain, the columns and the types against the data contracts of the consumers. 6. Portability: absolute paths and anything else that only runs on one machine. 7. Duplication: code that already exists in the project. 8. Architecture and performance: how it connects to the warehouse, what it loads into memory, what it scans. 9. Documentation: the runbook and the data contract for anything new. 10. Style: the project's code style. 11. For every finding: the risk, the file and line, the rule from the standards, and the suggested change. 12. The verdict: approve, or changes requested. Give the result as one web page. ## Pushback A finding the author declines stays in the report as declined, with the reason given. It is never dropped and never quietly downgraded. ## Output One HTML file, like [references/pr-review.html](references/pr-review.html): the change and its verdict on top, then every finding with the code, the rule and the suggested change, high risk first. Read it for the layout before you write the page. ## Reads - the change, the standards, the tests, the data contracts of the consumers ## Writes - the web page only ## Never - Never edits the change, never pushes, never merges.
© Data With Baraa · MIT · DataWithBaraa/claude-code-data-engineering-skills
Similar skills
All skills for Code review and refactoring →pr-review by other authors comes first.