code-review-guide
Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what's done well, and a clear approve / request-changes call — feedback that improves the code and the author.
npx skills add mohitagw15856/pm-claude-skills --skill code-review-guide --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.
# Code Review Guide Skill Bad code review nitpicks style while missing the design flaw, or dumps 40 ungraded comments. Good review is *prioritized* and *kind*: it catches what actually matters (correctness, security, design), separates blocking issues from nits, explains the *why*, and leaves the author better. This skill runs that review. ## Required Inputs Ask for these only if they aren't already provided: - **The change** — the diff/PR, and ideally its description/intent (what it's trying to do). - **Context** — language/stack, conventions, the part of the system it touches, risk level. - **Focus** (optional) — anything specific to scrutinize (security, performance, a tricky area). ## Output Format ### Review: [PR / change] **Summary** — in 1–2 lines: what the change does and your overall read (solid / needs work / risky). **Review passes** — scan in priority order and note findings: 1. **Correctness** — does it do what it claims? Edge cases, error handling, off-by-ones, concurrency. 2. **Security & data** — input validation, authz, secrets, injection, PII handling. 3. **Design** — is this the right approach? Coupling, the seam, simpler alternative, future pain. 4. **Tests** —
- Required Inputs
- Output Format
- Review: [PR / change]
- Quality Checks
- Anti-Patterns
- Based On
What does the code-review-guide skill do?
Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what's done well, and a clear approve / request-changes call — feedback that improves the code and the author.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill code-review-guide --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.