Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.

Repository
fabrik ↗
Licence
MIT
Last repository change
27.10.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 27.10.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

Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.

Original author description

Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.

How it works

  1. Method
  2. Surfacing issues
Original SKILL.md headings · 23 lines, 359 words
SKILL.md preview
---
name: code-review
description: Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.
license: MIT
---

# Code review

Always start by inspecting the changes. If you're on the `main` git branch, typically the (staged) git diff. If you're on a different branch, the committed and uncommitted changes compared to the main branch.

## Method

Please dispatch two subagents to carefully review the code changes. Run them on the most capable model available: in Claude Code, pass `model: fable`; in Codex, use `gpt-6-astra`. Reviewing is where depth pays off, regardless of which model wrote the code. Tell them that they're competing with another agent. Make sure they look at both architecture and implementation. Tell them that whoever finds more issues wins honour and glory.

Also have them run one targeted check on comments: read each new or changed comment as a reader who knows only this package and the public API of what it imports. Flag any mention of callers or importing packages, and any reference to internals hidden behind an abstraction the code consumes. Such context leakage is a real defect, not a comment nitpick -- surface it even when only one reviewer finds it.

Run a second targeted check on constants: flag any new package-level constant (or variable) that is used in only one place, or only within a single function. The fix is to inline the value at its use site, until a constant is genuinely needed -- reuse across functions, or a name that adds real meaning the literal lacks. Surface this even when only one reviewer finds it.

## Surfacing issues

Signal-to-noise ratio matters more than completeness. When reporting back to the caller:

- By default, only surface issues that **both** sub-agents independently found. Agreement between two reviewers is a strong signal that an issue is real.
- Drop issues that only one sub-agent raised, unless the issue is **serious** -- e.g. a correctness bug, security flaw, data-loss risk, concurrency hazard, or significant architectural problem. Serious issues get surfaced even without corroboration.
- Minor issues and nitpicks (style preferences, naming bikesheds, comment suggestions, micro-optimisations) should only be surfaced when both sub-agents flagged them.

State clearly in the report which issues had consensus and which are single-reviewer calls promoted for seriousness.

Versions

RepositoryScoreLicence
This page · maragudk/fabrik90MIT
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 ea4b0f0401b8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-review-gate
    Use when code has been written, before committing, or when merging a PR; also when the user says "review my code", "check before commit", "take a look at this change", "PR review", or asks for a strict review/merge gate.
  • 100review
    Review code quality, security, and maintainability before committing. Use when reviewing code changes, checking code quality, performing security review, or validating changes before commit.
  • 100api-review
    Reviews the specified code against the canonical API Design guidelines. Use this skill when the user asks for an API review or to check code against API design principles.
  • 100review-code
    Perform a senior-engineer code review when the user asks to review code, review a PR, review changes, or check code quality
  • 100pre-commit-review
    Review staged and unstaged changes before committing. Use when asked for a pre-commit review, a code-quality review of the current diff, or when a solve workflow requests an independent review.
  • 100review
    This skill should be used when the user asks to 'review changes', 'review my code', 'run a code review', 'review last commit', 'review recent changes', or 'check code against spec'.

Feedback and reports

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