Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.

Repository
honed ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 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.
Content25 / 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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.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

Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.

Original author description

Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.

How it works

  1. Read for intent first
  2. In order of importance
  3. Saying it
  4. Before you approve
Original SKILL.md headings · 22 lines, 194 words
SKILL.md preview
---
name: code-review
description: Use when reviewing a pull request or a diff, to find what matters (bugs, risk, missing tests) and say it so the author can act on it.
---

# Reviewing code

## Read for intent first
Read the PR description and any linked ticket before the diff. Review the change against what it claims to do; if it doesn't say, ask before guessing.

## In order of importance
1. **Correctness.** Wrong results, unhandled errors, edge cases (empty, null, very large, concurrent), off-by-one, resource leaks.
2. **Risk.** Security (input reaching queries, shells or HTML unescaped; secrets; authorization), data loss, migrations, anything hard to undo.
3. **Tests.** Does a test fail without this change? Are the risky paths covered?
4. **Design.** Does it fit how the codebase already does this? Is anything duplicated that exists already?
5. **Readability.** Names, size, clarity. Last, and only where it matters.

## Saying it
- Lead each comment with its weight: **blocking**, **should fix**, or **nit**.
- Point to the line, say what goes wrong and when, and suggest a fix when you have one.
- Ask instead of assert when you might be missing context.
- Don't comment on what a formatter or linter would catch.

## Before you approve
Run it or its tests if you can. Say plainly what you checked and what you didn't.

Versions

RepositoryScoreLicence
This page · dakotacolorado/honed90MIT
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 17e8ab907754 (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

  • 90code-review-and-quality
    Reviews a diff for correctness, risk, and missing evidence before merge. Use when preparing a change for commit, reviewing a pull request, reviewing AI-generated code, or deciding whether work is genuinely done.
  • 100review-pr
    Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".
  • 90review
    Review a pull request or diff for this repository against otari's project standards. Use when asked to review a PR, inspect a diff, or prepare review feedback.
  • 90dev-pr-review
    Use for reviewing a branch, pull request, local diff, or implementation plan before merge, including alignment of existing PR metadata with the diff and delivery state.
  • 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.
  • 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".

Feedback and reports

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