Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Reviews a code change (diff, PR or pasted code) for design, correctness, complexity, tests, naming, comments, style and docs, with prioritized feedback. Use when the user asks to review code, a pull request, or wants feedback before merging.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Reviews a code change (diff, PR or pasted code) for design, correctness, complexity, tests, naming, comments, style and docs, with prioritized feedback. Use when the user asks to review code, a pull request, or wants feedback before merging.

Original author description

Reviews a code change (diff, PR or pasted code) for design, correctness, complexity, tests, naming, comments, style and docs, with prioritized feedback. Use when the user asks to review code, a pull request, or wants feedback before merging.

How it works

  1. When to use
  2. Principles
  3. Workflow
  4. Output format
  5. Limits
Original SKILL.md headings · 60 lines, 418 words
SKILL.md preview
---
name: code-review
description: Reviews a code change (diff, PR or pasted code) for design, correctness, complexity, tests, naming, comments, style and docs, with prioritized feedback. Use when the user asks to review code, a pull request, or wants feedback before merging.
---

# Code review

Reviews a change the way mature engineering teams do: the goal is to **improve the overall health of the codebase** while keeping the author moving. The checklist and approval principle come from Google's public engineering practices. See `references/sources.md`.

## When to use
- "Review this PR / diff / function."
- Self-review before opening a PR.
- Not for rewriting the whole project; review the change in front of you.

## Principles
- Approve a change once it **definitely improves** code health, even if it isn't perfect. Don't block on minor polish.
- Never wave through a change that clearly makes code health worse.
- Technical facts and data outweigh opinions; the project's style guide decides style questions.
- Label low-importance remarks with **`Nit:`** so the author knows they are optional.

## Workflow

1. **Understand the change.** Read the description and the intent. If the intent is unclear, ask first.
2. **Look at the big picture.** Does this change belong here, and is the overall design sensible?
3. **Go through the checklist** (skip what is not relevant):
   - **Design:** do the pieces interact sensibly?
   - **Functionality:** does it do what the author intended, including edge cases and error paths?
   - **Complexity:** could it be simpler? Any over-engineering?
   - **Tests:** are there appropriate tests, are they correct, and would they fail if the code broke?
   - **Naming:** clear, not unwieldy?
   - **Comments:** do they explain *why*, and are they necessary?
   - **Style and consistency:** follows the style guide, then matches surrounding code.
   - **Documentation:** READMEs and docs updated if usage, build or release steps changed.
4. **Prioritize.** Separate must-fix issues from suggestions and nits.
5. **Be constructive.** Explain the reason for each comment and, where useful, suggest a concrete alternative. Comment on the code, not the person.
6. **Give a verdict:** approve, approve with nits, or request changes, and say why.

## Output format

```
## Summary
One or two sentences on the change and the verdict.

## Must fix
1. <file:line>: <issue>. Why it matters. Suggested fix.

## Should consider
- ...

## Nits (optional)
- Nit: ...

## What's good
- ...

## Verdict
Approve / Approve with nits / Request changes
```

## Limits
- Only reviews what was provided. State what was not visible (other files, tests, CI results).
- Does not run the code unless asked and able to; say so when a finding is based on reading only.
- Security-sensitive changes deserve a dedicated security review by a qualified person.
Files in this package (4)
  • SKILL.md 3 KB
  • skill.json 1 KB
  • references/examples.md 1 KB
  • references/sources.md 1 KB

Versions

RepositoryScoreLicence
This page · CaxCadu/multipla-skills100MIT
microsoft/aspire100MIT
kdlbs/kandev100AGPL-3.0
dotnet/runtime100MIT
drosam/agents100MIT
ggml-org/llama.cpp100MIT
ShamelesAbyss/Nyx100Apache-2.0
dzhng/jevgrep100MIT
iuliandita/skills100MIT

Database snapshot: 13.11.2026 · package version 62cb3ba87571 (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

  • 90reviews
    Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change".
  • 100check-the-code
    Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.
  • 100local-awesome-code-review-682d95be
    Reviews a diff, patch or pull request for correctness, security and team standards, with confidence-scored findings in severity buckets (Critical / Suggestions / Nice to have). Use when asked to review a change, before merging, after finishing a feature, or 'сделай ревью'. Do…
  • 80Code review
    Review a diff or module for correctness, security, regressions, and missing tests. Use when the user asks for a review or before shipping a change.
  • 90ce-code-review
    Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.
  • 95pr-review
    Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.