Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Use when asked to review, audit, clean up or simplify code or a pull request.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 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 13.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 asked to review, audit, clean up or simplify code or a pull request.

Original author description

Use when asked to review, audit, clean up or simplify code or a pull request.

How it works

  1. Order of work
  2. What to look for, most important first
  3. Rules
Original SKILL.md headings · 20 lines, 199 words
SKILL.md preview
---
name: code-review
description: "Use when asked to review, audit, clean up or simplify code or a pull request."
version: 1.0.0
category: dev
author: Macron (adapted from Hermes Agent)
license: MIT
---

# Code review

## Order of work
1. Understand the intent: what is this code (or change) supposed to do? Read the README, the entry point and the tests first (`project_tree`, `code_outline`).
2. Run it: build, lint and test (`bash_execute`). A review that never ran the code guesses.
3. Read the changed code top-down, then every caller of what changed (`search_code`).

## What to look for, most important first
1. **Correctness**: wrong logic, off-by-one, unhandled errors, nil/None, empty input, unicode, time zones, concurrency (shared state, races).
2. **Security**: injection (SQL, shell, path), secrets in code, missing auth checks, unsafe deserialization, SSRF.
3. **Data loss**: writes without transactions, partial files (write to a temp file, then rename), deletes without checks.
4. **Performance** only where it matters: N+1 queries, work inside hot loops, unbounded memory.
5. **Simplicity**: dead code, duplicated logic, needless layers, names that lie. Prefer deleting code to adding it.

## Rules
- Every finding: file:line, what is wrong, a realistic input that breaks it, and the fix. No vague "consider improving".
- Separate must-fix from nice-to-have. Say what is good, briefly.
- When asked to fix: small changes with `edit_file`, run the tests again, show the real output.

Versions

RepositoryScoreLicence
This page · Metixpro/Macron-Agent86MIT
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 cf1d00bdcf05 (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

  • 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".
  • 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".
  • 100review
    Use when asked to review a pull request or merge request, examine code changes, find bugs, or audit a branch, in standard or depth mode. Not for an iterative review-and-fix loop: use audit-project.
  • 90review-a-pull-request
    A careful code review of a change, a branch or a pull request: correctness, tests, security, readability, with findings ordered by how much they matter. Use when the owner asks you to review code, a diff, a branch or a PR.
  • 82review-code
    Use to review code.
  • 100cpp-review
    Review C++ code against Google C++ Style Guide. Use when reviewing C++ code, pull requests, or when asked to check code style compliance.

Feedback and reports

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