Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Pull request review guidance for correctness, security, tests, performance, API contract drift, migrations, and error handling. Use when reviewing diffs, pull requests, or risky refactors.

Licence
MIT
Last repository change
12.05.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 12.05.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

Pull request review guidance for correctness, security, tests, performance, API contract drift, migrations, and error handling. Use when reviewing diffs, pull requests, or risky refactors.

Original author description

Pull request review guidance for correctness, security, tests, performance, API contract drift, migrations, and error handling. Use when reviewing diffs, pull requests, or risky refactors.

How it works

  1. When to Activate
  2. Review Order
  3. Blocking vs Suggestion
  4. What to Check
  5. Tone
  6. Checklist
Original SKILL.md headings · 75 lines, 443 words
SKILL.md preview
---
name: code-review
description: Pull request review guidance for correctness, security, tests, performance, API contract drift, migrations, and error handling. Use when reviewing diffs, pull requests, or risky refactors.
---

# Code Review

Review code for correctness first, then for safety, operability, and maintainability.

## When to Activate

- Review a pull request before approval
- Audit a migration or rollout plan
- Check for missing tests on changed logic
- Evaluate API or schema contract changes
- Inspect security-sensitive authentication code
- Separate blockers from optional cleanup
- Summarize review findings for a teammate

## Review Order

| Priority | Check |
| --- | --- |
| 1 | Logic correctness and regression risk |
| 2 | Security, privacy, and data integrity |
| 3 | Test coverage and validation gaps |
| 4 | Performance, scaling, and resource usage |
| 5 | Style, naming, and cleanup |

## Blocking vs Suggestion

| Comment Type | Use When | Prefix |
| --- | --- | --- |
| Blocking | Incorrect behavior, security hole, migration risk, broken contract | `Blocking:` |
| Suggestion | Readability improvement, minor cleanup, non-critical refactor | `Suggestion:` |
| Question | Intent or assumption is unclear | `Question:` |

## What to Check

| Area | Questions |
| --- | --- |
| Logic | Are edge cases, retries, and failure paths handled? |
| Security | Are auth checks, secrets, and untrusted inputs handled safely? |
| Tests | Do tests cover new behavior and likely regressions? |
| Performance | Does this add N+1 queries, repeated allocations, or hot-loop work? |
| API contracts | Will clients or jobs break on shape changes? |
| Migrations | Is rollout safe across old and new code versions? |
| Error handling | Are failures explicit, typed, and observable? |

## Tone

| Preferred | Avoid |
| --- | --- |
| Direct, specific, file-scoped feedback | Vague comments like "this feels wrong" |
| Explain impact | Nitpicks framed as blockers |
| Offer a fix path when practical | Personal or emotional language |

BAD

```text
This code is bad. Please redo.
```

GOOD

```text
Blocking: [payments/service.ts] charge retries on 500 but not on timeout, so transient network failures can still drop payments. Add retry handling for socket timeout errors and cover it with a test.
```

## Checklist

- [ ] Logic changes were checked against edge cases and failure paths
- [ ] Security-sensitive code paths were reviewed explicitly
- [ ] New behavior has sufficient test coverage
- [ ] Performance-sensitive paths were inspected for regressions
- [ ] API contract changes are documented and compatible
- [ ] Migrations are safe for mixed-version deploys
- [ ] Feedback is labeled as blocking, suggestion, or question

Versions

RepositoryScoreLicence
This page · kid-sid/codex-spellbook100MIT
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 df0b55478294 (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

  • 100pr-review
    Structured review of a pull request or the current diff - correctness, contract drift, security, missing tests, coverage gate - producing classified findings and a verdict. Use when the user asks to review a PR or diff, or as the self-review step of the story workflow.
  • 90review
    Review changed code for correctness, security, simplicity, maintainability, tests, performance, and approved-spec compliance. Use for pull requests, diffs, implementation reviews, or security-focused code audits.
  • 100review
    Review a ClickHouse Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.
  • 100review-pr
    Review a pull request for correctness, architecture, security, and test coverage. Use when the user names a PR number to review.
  • 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.
  • 100code-review-specialist
    Comprehensive code review with security, performance, and quality analysis. Use when users ask to review code, analyze code quality, evaluate pull requests, or mention code review, security analysis, or performance optimization.

Feedback and reports

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