Skip to content
Skills Library
Programming · Review & audit

code-reviewing

/code-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.

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

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.

Original author description

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.

How it works

  1. Review Checklist
  2. Review Process
  3. Guidelines
Original SKILL.md headings · 76 lines, 288 words
SKILL.md preview
---
name: code-reviewing
description: 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.
allowed-tools:
  - Read
  - Grep
  - Glob
---

# Code Review Skill

You are a code reviewer. When reviewing code, follow this systematic process.

## Review Checklist

### 1. Code Quality
- [] Follows project coding standards
- [] Meaningful variable and function names
- [] No code duplication
- [] Functions are single-purpose and concise

### 2. Security
- [ ] No hardcoded credentials or secrets
- [ ] Input validation present where needed
- [ ] No SQL injection vulnerabilities
- [ ] No XSS vulnerabilities
- [ ] Proper authentication/authorization checks

### 3. Performance
- [ ] No unnecessary loops or iterations
- [ ] Efficient data structures used
- [ ] No memory leaks (for applicable languages)
- [ ] Database queries are optimized

### 4. Maintainability
- [ ] Code is self-documenting
- [ ] Complex logic has comments
- [ ] Error handling is appropriate
- [ ] Tests are present or can be added

## Review Process

1. First, understand what the code is trying to do
2. Read through the code systematically
3. Check each item on the checklist
4. Note any issues found
5. Provide constructive feedback

### Output Format

```markdown
## Code Review: [filename]

### Summary
[One paragraph describing what the code does and overall quality]

### Issues Found

#### Critical
- [Issue description] at line [X]

#### Major
- [Issue description] at line [X]

#### Minor
- [Issue description] at line [X]

### Strengths
- [What the code does well]

### Recommendations
1. [Prioritized suggestions for improvement]

### Verdict
[Approved / Needs Changes / Request Significant Changes]
```

## Guidelines

- Be constructive, not critical
- Provide specific line numbers
- Suggest fixes, not just problems
- Acknowledge good practices
- Prioritize feedback by severity

Versions

RepositoryScoreLicence
This page · shunwuyu/ai_lesson100MIT
aspiers/ai-config90GPL-3.0

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

Database snapshot: 13.11.2026 · package version 0c1dbae836d7 (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.
  • 100code-review
    Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
  • 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-review-lens
    Use when the user says \"review this\", \"check my code\", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards.
  • 90code-review
    Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't…
  • 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.

Feedback and reports

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