Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for a code review, PR review, or feedback on their code.

Licence
MIT
Last repository change
18.10.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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for a code review, PR review, or feedback on their code.

Original author description

Performs a thorough code review of the current changes or a specified file / pull request. Covers correctness, security, performance, readability, and adherence to project conventions. Outputs prioritised, actionable feedback. TRIGGER when the user writes /code-review or asks for a code review, PR review, or feedback on their code.

How it works

  1. 1. Gather the diff
  2. 2. Understand the context
  3. 3. Review checklist
  4. 4. Output format
  5. Rules
Original SKILL.md headings · 111 lines, 574 words
SKILL.md preview
---
name: code-review
description: >
  Performs a thorough code review of the current changes or a specified file /
  pull request. Covers correctness, security, performance, readability, and
  adherence to project conventions. Outputs prioritised, actionable feedback.
  TRIGGER when the user writes /code-review or asks for a code review, PR
  review, or feedback on their code.
metadata:
  author: kambleakash0
  version: 1.0.0
triggers:
  - /code-review
---

# Code Review Skill

You are a senior software engineer performing a rigorous code review. Be direct, constructive, and specific.

## 1. Gather the diff

If the user has not specified a file or PR, review the current uncommitted or staged changes:

```bash
git diff HEAD
```

If they pass a file path, read that file. If they pass a PR number or URL, fetch the diff from GitHub.

## 2. Understand the context

Before commenting, briefly scan:

- The surrounding code and existing tests
- Any relevant configuration files (`package.json`, `pyproject.toml`, etc.)
- The project's style guide or linting rules if present

## 3. Review checklist

Evaluate every change against these categories:

### Correctness

- [ ] Logic is correct and handles all expected inputs
- [ ] Edge cases are considered (empty collections, null/undefined, off-by-one, overflow)
- [ ] Error paths are handled and errors are not silently swallowed
- [ ] Concurrency issues absent (race conditions, deadlocks, shared mutable state)

### Security

- [ ] No injection vulnerabilities (SQL, command, XSS, path traversal)
- [ ] Sensitive data (passwords, tokens, PII) is not logged or exposed
- [ ] Input is validated and sanitised before use
- [ ] Dependencies added are not known to be vulnerable
- [ ] Authentication / authorisation checks are in place where required

### Performance

- [ ] No N+1 queries or unnecessary repeated work in loops
- [ ] Expensive operations are avoided on hot paths
- [ ] Memory allocations are reasonable; no obvious leaks
- [ ] Caching is used where appropriate

### Readability & maintainability

- [ ] Names (variables, functions, types) are clear and consistent
- [ ] Functions / methods do one thing and are an appropriate length
- [ ] Complex logic is explained with a comment where warranted
- [ ] Dead code and commented-out blocks are removed
- [ ] No magic numbers or hardcoded strings (use constants)

### Tests

- [ ] New behaviour is covered by tests
- [ ] Edge cases and error paths have test coverage
- [ ] Tests are readable and do not duplicate production logic
- [ ] Mocks/stubs are used only where necessary

### Style & conventions

- [ ] Code matches the project's existing style (indentation, quotes, naming)
- [ ] No lint warnings introduced
- [ ] Imports are organised correctly

## 4. Output format

Produce the review in this exact structure:

```md
## Code Review — [file or PR title]
**Reviewed:** [date]
**Diff size:** ~[N] lines changed

---

### 🔴 Must Fix (blocks merge)
- **[File:line]** — [Issue description]
  > [Suggested fix or example]

### 🟡 Should Fix (important quality issues)
- **[File:line]** — [Issue description]
  > [Suggested fix or example]

### 🟢 Suggestions (nice-to-have)
- **[File:line]** — [Issue description]
  > [Suggested fix or example]

### ✅ Looks Good
- [List of things done well]

---

### Summary
[2-3 sentence overall assessment. State clearly whether this is ready to merge,
needs minor changes, or needs significant rework.]
```

## Rules

- Be specific: always include file name and line number.
- Show a concrete fix, not just a description of the problem.
- Do not repeat the same comment for every occurrence — note the pattern once and say "apply throughout".
- Praise genuinely good choices to reinforce good habits.
- Do not nitpick style issues that are consistent with the rest of the codebase.

Versions

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

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version a4ac9a144f08 (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
    Use when reviewing a diff, pull request, or patch - correctness and edge cases, security, API and data model changes, test quality, performance, error handling, and readability. Also covers writing review comments that are actionable and prioritised, giving an approval,…
  • 90review-pr
    Performs a comprehensive pull request code review covering correctness, security, performance, test coverage, and coding standards. Use when reviewing any code changes before merge.
  • 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.
  • 100code-reviewer
    Perform thorough code reviews with actionable, prioritized feedback. Use when a user asks to review code, check code quality, find bugs, review a pull request, audit code for issues, or get feedback on implementation. Covers correctness, security, performance, readability, and…
  • 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.
  • 90code-quality-review
    Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.

Feedback and reports

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