diff-review-strategy
PR size-based review depth, performance review checklist, architecture conformance checks, and framework-specific review patterns.
npx skills add vibeeval/vibecosystem --skill diff-review-strategy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Diff Review Strategy ## PR Size Categories and Review Depth | Category | Lines Changed | Review Depth | Action | |----------|--------------|--------------|--------| | XS | 1–10 | Quick scan | Auto-approve if tests pass, typo/doc fixes | | S | 11–50 | Focused | Check edge cases, naming, one logic path | | M | 51–200 | Thorough | Full logic review, design check, test coverage | | L | 201–500 | Walkthrough | Request author explanation, check design first | | XL | 500+ | Split required | Block merge, ask to split into logical units | ### XS/S review checklist ``` [ ] Does the change do exactly what the title says? [ ] Are edge cases handled (null, empty, out-of-range)? [ ] Are variable names clear? [ ] Are tests updated or added? ``` ### M review checklist ``` [ ] Is the design the simplest solution? [ ] Are error paths handled? [ ] Is there duplication that should be extracted? [ ] Does it follow existing patterns in the codebase? [ ] Are there security implications (user input, auth)? [ ] Is the test coverage meaningful (not just happy path)? ``` ### L/XL protocol ``` 1. Read the PR description and linked ticket first 2. Review architecture/design before line-by-line reading 3. Req
- PR Size Categories and Review Depth
- XS/S review checklist
- M review checklist
- L/XL protocol
- Performance Review Checklist
- Database
- React / Frontend
- General backend
- Architecture Conformance Checks
- Layer violation detection
- Dependency direction (clean architecture)
- Feature coupling detection
- Framework-Specific Review Patterns
- React
What does the diff-review-strategy skill do?
PR size-based review depth, performance review checklist, architecture conformance checks, and framework-specific review patterns.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill diff-review-strategy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.