code-review
/code-review
Review code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.
Original author description
Review code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.
How it works
- Method
- Reporting format
- Boundaries
SKILL.md preview
---
name: code-review
description: Review code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.
---
# Code review
Review the change, not the author, and report only what you can defend with
evidence from the code in front of you.
## Method
1. **Understand the intent first.** Read the description, the tests, and the
shape of the diff before judging a line. A "bug" that is deliberate
behavior wastes everyone's time; state the intent back in one sentence
before your first finding.
2. **Read in execution order, not file order.** Follow a request, event, or
call from entry to exit through the changed code. Bugs live on the paths
between hunks, not inside them.
3. **Hunt in this priority order:**
- Correctness: logic inversions, off-by-one, unhandled error and `null`
paths, race conditions, resource leaks, broken invariants.
- Security: unvalidated input reaching queries, paths, URLs, or shell;
secrets in code; authz checks missing on new surfaces.
- Reliability: what happens when the network call fails, the file is
missing, the input is empty, the list has one item, or two callers
arrive at once.
- Maintainability: misleading names, dead code, duplication of an
existing helper, missing tests for the risky branch.
4. **Verify before you report.** For each candidate finding, construct the
concrete failing scenario: the input or state that triggers it and the
wrong result that follows. If you cannot construct one, it is a question,
not a finding: ask it as a question.
5. **Rank by severity, worst first.** Blocker (data loss, security,
crash), Major (wrong behavior on realistic input), Minor (confusing but
correct), Nit (style). Never bury a Blocker under ten Nits.
## Reporting format
For each finding: **file:line: one-sentence defect: the failing scenario,
a suggested fix.** Lead with the verdict: "N findings, worst is X" so the
reader knows the stakes in the first line. If the change is good, say so
plainly and stop; inventing findings to look thorough is a defect in the
review, not the code.
## Boundaries
- Do not review style a formatter or linter already enforces.
- Do not demand rewrites of working code that is merely not how you would
write it; that is preference, and it goes at Nit level or not at all.
- If the diff is too large to follow execution paths, say that first: "this
needs splitting to review honestly" is a legitimate top finding.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Amey-Thakur/AI-SKILLS | 90 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 280736f001ba (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100awesome-code-review
Reviews a diff, patch or pull request for correctness, security and team standards, with severity-ranked findings. Use when asked to review a change or PR, or before merging. - 100code-review-evidence
Use when before merging a PR or after a nontrivial code change. Review a change for correctness, security, maintainability and scope fit with reproducible findings. Do not use when pure copy editing with no executable code or system behavior. - 100audit-code-review
Review a PR or diff for correctness, security, and maintainability. Use for a pull request, a named change set, or "review my changes". Repo-wide anti-patterns → audit-code-quality. Bulk transforms → audit-codemod-safety. - 90code-reviewing
Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge. - 100code-reviewer
Reviews a code diff or pull request for correctness bugs, security vulnerabilities, and quality/maintainability problems, producing severity-ranked findings with file/line references and concrete fix suggestions. Use this skill when the user asks to "review this PR", "review my… - 100dev-review
Use when a diff, branch or PR needs review before merge, on correctness, standards and the spec.