code-review-expertlisted

Expert code review with a senior engineer lens — covers architecture, SOLID principles, security vulnerabilities, performance, error handling, testing gaps, and API contract changes. Use this skill whenever the user asks to review code, check changes, audit a diff, look over a PR, find bugs in their work, or wants feedback on code quality. Also trigger when the user says things like 'review my changes', 'check this before I push', 'what do you think of this code', 'any issues with this?', 'code review', 'look this over', or 'is this ready to merge'. Works with any programming language and any size of change.
kevinlin/skills · ★ 3 · Code & Development · score 74

Install: claude install-skill kevinlin/skills

# Code Review Expert ## Overview Perform a structured, senior-engineer-level review of code changes. Adapt your depth and focus based on what actually changed — a 5-line bug fix gets a focused review, while a 500-line feature branch gets a broader architectural pass. Default to review-only output. Do not implement fixes unless the user explicitly asks. ## Severity Levels | Level | Name | Description | Action | |-------|------|-------------|--------| | **P0** | Critical | Security vulnerability, data loss risk, correctness bug | Must fix before merge | | **P1** | High | Logic error, major design issue, performance regression | Should fix before merge | | **P2** | Medium | Code smell, maintainability concern, missing tests | Fix now or create follow-up | | **P3** | Low | Style, naming, minor suggestion | Optional improvement | ## Workflow ### 1. Scope the changes Determine what's being reviewed: - **Default (unstaged + staged changes)**: Run `git diff --stat` and `git diff` to see what changed. If empty, check staged changes with `git diff --cached --stat` and `git diff --cached`. If still empty, ask the user what they want reviewed. - **Specific files or commits**: If the user points to files or a commit range, scope to that. - **Branch/PR review**: If the user mentions a PR or branch, diff against the target branch (e.g., `git diff main...HEAD`). Use the Grep and Glob tools to find related code, callers, and contracts when you need more context around the changes.