Skip to content
Skills Library
Programming · Review & audit

Code review

/Code 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.

Repository
blank ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

80/ 100Class: good
Format15 / 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 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

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.

Original author description

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.

How it works

  1. 1. Establish the change
  2. 2. Look for what breaks
  3. 3. Output
  4. Guardrails
Original SKILL.md headings · 37 lines, 274 words
SKILL.md preview
---
name: Code review
description: 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.
---

# Code review

Review for truth, not for style points. A short review that finds the real bug beats a long checklist.

## 1. Establish the change

- Identify the exact diff (`git diff`, `git diff --staged`, or the files named).
- Read the full surrounding function and its callers — not only changed lines.
- Note the intent: bug fix, feature, refactor, or dependency bump.

## 2. Look for what breaks

In priority order:

1. **Correctness** — wrong state, off-by-one, race conditions, unhandled null/error paths, incorrect async ordering, stale closures.
2. **Security** — injection (SQL, shell, HTML), missing authorization, secret exposure, unsafe deserialization, path traversal, SSRF.
3. **Data** — migrations that lose data, missing transactions, non-idempotent retries, N+1 queries in hot paths.
4. **Compatibility** — public API changes, schema drift, platform differences, version constraints.
5. **Tests** — behavior changed without a failing test that now passes. Suggest the smallest meaningful test.

Do not report pure preference (formatting, naming taste) unless it obscures meaning. Do not invent issues to seem thorough.

## 3. Output

- Start with a one-line verdict: ship / ship with nits / needs work.
- List findings by severity: `blocker`, `major`, `minor`.
- Each finding: `path:line` → what happens → why it matters → minimal fix.
- Separate **questions** from findings when intent is unclear.
- If there are no issues, say so plainly and name what you verified.

## Guardrails

- Never modify code during a review unless asked. Offer a patch instead.
- Read tests and relevant call sites before claiming a regression.
- If the diff is too large to review meaningfully, say which files you covered.

Versions

RepositoryScoreLicence
This page · purplemacaron/blank80MIT
adobe/helix-tools-website90Apache-2.0
Karanlikyolcu/Skils90MIT

Database snapshot: 13.11.2026 · package version bff300a12204 (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
    Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change.
  • 100code-review
    Use when reviewing a proposed change for correctness, regressions, security implications, data integrity, compatibility, or missing verification.
  • 90doompi-review
    Review a code change for concrete defects, regressions, missing tests, and contract violations. Use when the user asks for code review, diff review, or risk assessment, not as a general implementation workflow.
  • 90estack-review
    Review an Elixir/Phoenix diff for correctness, security, concurrency, and regressions. Use when reviewing a PR or checking changes before committing or deployment.
  • 100code-review
    Review C code changes for correctness, safety, and style. Use this when you want to review C code changes or PRs.
  • 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.