pr-review

Solid

Use when a pull request or git diff is ready and you need a thorough review covering bugs, security, tests, and style before it is merged.

Code & Development 1 stars 0 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
38
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# PR Review ## When to use Use this skill on every PR before merge, or when the user asks "review my changes". ## Steps 1. Read the full diff and the linked issue or context. 2. Check correctness: off-by-one, null handling, concurrency, error paths. 3. Check security: input validation, authz, secrets, unsafe deserialization. 4. Check coverage: are the changed behaviours tested? Add suggested tests. 5. Check style and clarity, but only when it affects maintainability. 6. Return a prioritized list: must-fix, should-fix, nit. ## Examples - "Review this PR for correctness and missing tests" - "What could break in this diff?" ## References Separate blocking issues from nits; quote the exact lines and give a concrete fix, not just a complaint.

Details

Author
NSBen
Repository
NSBen/skillfoundry
Created
5 days ago
Last Updated
5 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category