Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes.

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

Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes.

Original author description

Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes.

How it works

  1. Review Dimensions
  2. Output Format
  3. Workflow
  4. Behavioral Guidelines
Original SKILL.md headings · 47 lines, 246 words
SKILL.md preview
---
name: code-review
description: "Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes."
---

# Code Review Skill

Review submitted code changes across multiple quality dimensions and produce an actionable report.

## Review Dimensions

1. **Correctness** — Is the logic correct? Are edge cases handled?
2. **Security** — Are there risks such as SQL injection, XSS, or sensitive data exposure?
3. **Performance** — Are there unnecessary loops, memory leaks, or N+1 queries?
4. **Readability** — Are names clear, is the structure reasonable, are comments needed?
5. **Consistency** — Does it follow the project's existing coding style?

## Output Format

Review results are categorized by severity:

- **Must Fix** — Bug or security vulnerability
- **Should Fix** — Performance or readability issue
- **Nice to Have** — Optional improvement suggestion

Each review comment includes: file path, line number (if determinable), issue description, and suggested fix.

### Example Review Comment

```
**Must Fix** — src/auth/login.ts:42
Issue: User-supplied `redirectUrl` is passed to `res.redirect()` without validation, enabling an open-redirect attack.
Suggested fix:
  const allowed = ['/', '/dashboard', '/settings'];
  const target = allowed.includes(redirectUrl) ? redirectUrl : '/';
  res.redirect(target);
```

## Workflow

1. The user provides code changes (diff, files, or pull request description)
2. Review file by file across all dimensions
3. Output the review report to the `reviews/` directory
4. Summarize: approved / changes requested / blocked

## Behavioral Guidelines

- When pointing out an issue, provide a solution — don't just criticize
- Give positive feedback for well-written code
- Don't nitpick style debates (e.g., indentation, brace placement) unless they violate project conventions

Versions

RepositoryScoreLicence
This page · 0xranx/golembot100MIT
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 ca3683530248 (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

  • 100code-reviewer
    Reviews pull requests and code changes for quality, security, and best practices. Use when user asks for code review, PR review, or mentions reviewing changes.
  • 84review-code
    Review code changes for quality, security, and performance. Use when user says "review my changes", "do a code review", "check this for issues", "analyze code quality", "security review", "performance review", "is this PR ready", or needs architecture, security, performance, and style analysis.
  • 100pr-review-expert
    Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.
  • 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.
  • 100code-reviewer
    Review GitHub pull requests, diffs and code changes for evidence-based correctness, data integrity, security, compatibility, performance and test risks. Use when the user asks for a code review or pre-merge risk assessment. Never modify code or approve or merge a PR implicitly.
  • 100pr-review-expert
    Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.

Feedback and reports

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