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 4 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

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: 4 days ago
Last Updated: 4 days ago
Language: Python
License: MIT

Integrates with

GitHub · DevTools

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

code-review

Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards.

7 Updated today

event4u-app

Code & Development Listed

pr-review

Deep review of someone else's pull request in an isolated worktree — hunts the failures that automated review misses (broken error paths, infinite loops, races, blast radius, claim-vs-code drift), deduplicates against the bot's comments, and gives a short verdict in chat. Read-only; never edits, pushes or posts.

0 Updated today

grinchenkoedu

Code & Development Listed

pr-review-guardian

Review a pull request or code diff for correctness, security, and performance, returning a structured verdict with severity-tagged findings. Use this whenever the user shares a diff, PR link, or code change and asks for review, feedback, "is this safe to merge", "look this over before I ship", or mentions code review, even if they don't say the words "pull request".

0 Updated 1 weeks ago

moses607