Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Reviews code changes for bugs, style issues, security vulnerabilities, and best practices. Use when reviewing PRs, checking code quality, or validating implementations.

Licence
GPL-3.0
Last repository change
07.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 07.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Reviews code changes for bugs, style issues, security vulnerabilities, and best practices. Use when reviewing PRs, checking code quality, or validating implementations.

Original author description

Reviews code changes for bugs, style issues, security vulnerabilities, and best practices. Use when reviewing PRs, checking code quality, or validating implementations.

How it works

  1. When to Use This Skill
  2. Review Checklist
  3. How to Provide Feedback
  4. Decision Tree
  5. Example Review Comments
  6. Best Practices
Original SKILL.md headings · 123 lines, 582 words
SKILL.md preview
---
name: code-review
description: Reviews code changes for bugs, style issues, security vulnerabilities, and best practices. Use when reviewing PRs, checking code quality, or validating implementations.
---

# Code Review Skill

Systematic approach to reviewing code changes for quality, correctness, and maintainability.

## When to Use This Skill

- Reviewing pull requests or merge requests
- Checking code quality before committing
- Validating implementation against requirements
- Finding potential bugs or security issues
- Ensuring code follows project conventions

## Review Checklist

### 1. Correctness
- [ ] Does the code do what it's supposed to do?
- [ ] Are edge cases handled properly?
- [ ] Are error conditions handled gracefully?
- [ ] Is the logic correct and complete?

### 2. Security
- [ ] No hardcoded credentials or secrets
- [ ] Input validation is present
- [ ] SQL injection prevention (parameterized queries)
- [ ] XSS prevention (proper escaping)
- [ ] Authentication/authorization checks

### 3. Code Quality
- [ ] Follows project coding standards
- [ ] Meaningful variable and function names
- [ ] No code duplication (DRY principle)
- [ ] Functions are focused and single-purpose
- [ ] Proper use of comments (why, not what)

### 4. Performance
- [ ] No obvious inefficiencies (N+1 queries, etc.)
- [ ] Appropriate data structures used
- [ ] Caching considered where appropriate
- [ ] No memory leaks or resource leaks

### 5. Maintainability
- [ ] Code is readable and self-documenting
- [ ] Complex logic is well-commented
- [ ] Tests are included for new functionality
- [ ] Documentation updated if needed

## How to Provide Feedback

### Be Specific
```diff
- ❌ "This code is wrong"
+ ✅ "The null check on line 42 should happen before accessing user.name"
```

### Explain Why
```diff
- ❌ "Use const instead of let"
+ ✅ "Use const instead of let since this value is never reassigned"
```

### Suggest Alternatives
```diff
- ❌ "This is inefficient"
+ ✅ "Consider using a Map instead of array.find() for O(1) lookup"
```

### Use Appropriate Severity

| Prefix | Meaning |
|--------|---------|
| `🔴 BLOCKER:` | Must fix before merge |
| `🟠 SHOULD:` | Should fix, but not blocking |
| `🟡 COULD:` | Nice to have improvement |
| `💡 NIT:` | Minor style preference |
| `❓ QUESTION:` | Need clarification |

## Decision Tree

```
Is this a critical/security issue?
├── YES → 🔴 BLOCKER - Must fix
└── NO
    ├── Does it affect functionality?
    │   ├── YES → 🟠 SHOULD - Fix recommended
    │   └── NO
    │       ├── Improves code quality?
    │       │   ├── YES → 🟡 COULD - Nice improvement
    │       │   └── NO → 💡 NIT - Optional
```

## Example Review Comments

### Good Example
```
🔴 BLOCKER: SQL Injection vulnerability

The user input is directly interpolated into the SQL query on line 87:
`db.query(`SELECT * FROM users WHERE id = ${userId}`)`

Please use parameterized queries instead:
`db.query('SELECT * FROM users WHERE id = ?', [userId])`
```

### Another Example
```
🟡 COULD: Consider extracting to helper function

Lines 45-60 duplicate the validation logic from AuthService.
Consider extracting to a shared helper:

`const isValidEmail = (email) => /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email);`
```

## Best Practices

1. **Review in context** - Understand the PR's purpose before diving into code
2. **Be constructive** - Focus on the code, not the person
3. **Acknowledge good work** - Praise well-written code
4. **Ask questions** - If unsure, ask rather than assume
5. **Keep it focused** - Don't bring up unrelated issues
6. **Be timely** - Review promptly to unblock teammates

Versions

RepositoryScoreLicence
This page · Funnyhust/POC_Kaenx_Creator100GPL-3.0
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 d303e1937b8d (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.
  • 100git-pr-reviewer
    Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.
  • 100review
    Perform a comprehensive code review on a GitHub pull request. Use when the user asks to review a PR, review code changes, check a pull request for quality, security, bugs, or best practices, or provides a PR number or GitHub PR URL to review.
  • 100do-code-review
    Reviews code changes in azure-ai-ml package for quality, Azure SDK compliance, and best practices. Use when reviewing code, checking pull requests, or when user asks to review changes or check code quality in azure-ai-ml.
  • 100code-reviewer
    Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.
  • 100code-reviewing
    Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.

Feedback and reports

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