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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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.
…
The line at the top of this page pins the label git:20261029.2e2b6c2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_py3ye7rlqqkcyylv
GET https://markdownregistry.com/api/v1/resolve?ref=datawithbaraa/claude-code-data-engineering-skills/pr-review
GET https://markdownregistry.com/api/v1/blob/c4605c8f38764c555f57c801ca41af3d3252782583d5e13c5da66b3e8a54b434
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
datawithbaraa/claude-code-data-engineering-skills · skills/big-review/SKILL.md · Use once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs…
datawithbaraa/claude-code-data-engineering-skills · skills/contract/SKILL.md · Use when a new source is connected or a source changes how it delivers, to write the data contract with the source…
datawithbaraa/claude-code-data-engineering-skills · skills/cost-review/SKILL.md · Use for the monthly cost review of the platform, to see where the compute and the storage money goes, per job, pipeline…
datawithbaraa/claude-code-data-engineering-skills · skills/data-product/SKILL.md · Use when a table is served to consumers, released or changed, to build everything a consumer needs as a data product…
datawithbaraa/claude-code-data-engineering-skills · skills/docs/SKILL.md · Use after a change or a release, to write and refresh the runbook and the how-to guides of the project, so the runbook…
datawithbaraa/claude-code-data-engineering-skills · skills/impact/SKILL.md · Use before you change a table, a column or a function, to see what it is built from, what depends on it, who reads it…
datawithbaraa/claude-code-data-engineering-skills · skills/incident/SKILL.md · Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two…
datawithbaraa/claude-code-data-engineering-skills · skills/knowledge-refresh/SKILL.md · Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the…
datawithbaraa/claude-code-data-engineering-skills · skills/metadata/SKILL.md · Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types…
datawithbaraa/claude-code-data-engineering-skills · skills/migration/SKILL.md · Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the…
datawithbaraa/claude-code-data-engineering-skills · skills/profile/SKILL.md · Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the…
agentic-community/mcp-gateway-registry · .claude/skills/pr-review/SKILL.md · Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and…
athola/claude-night-market · plugins/sanctum/skills/pr-review/SKILL.md · Reviews pull requests with scope validation, requirements compliance, and line comments. Use when reviewing GitHub or…
mathews-tom/armory · evals/skillsbench/source-snapshots/pr-review-776a618c/SKILL.md · Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with…
mathews-tom/armory · skills/pr-review/SKILL.md · Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with…
