Skip to content
Back to skills

Community Code Reviewer

ASecurity

Perform thorough, constructive code reviews on pull requests and code changes. Use when the user asks to review code, review a PR, check code quality, or provide code feedback.

  • 666 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added February 8, 2026
code-qualitygosqltestingcode-reviewsecurityperformance

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill community-code-reviewer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Community Code Reviewer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Community Code Reviewer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-community-code-reviewer/badge)](https://www.skillsdirectory.com/skills/majiayu000-community-code-reviewer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: community-code-reviewer
description: Perform thorough, constructive code reviews on pull requests and code changes. Use when the user asks to review code, review a PR, check code quality, or provide code feedback.
---

# Code Review Skill

Perform thorough, constructive code reviews on pull requests and code changes.

## Instructions

When reviewing code:

### 1. First Pass - Understanding
- Read the PR description and linked issues
- Understand the intent and context
- Identify the scope of changes

### 2. Check for Issues

**Correctness**
- Logic errors or bugs
- Edge cases not handled
- Race conditions or concurrency issues
- Null/undefined handling

**Security**
- Input validation
- SQL injection, XSS vulnerabilities
- Hardcoded secrets or credentials
- Proper authentication/authorization

**Performance**
- Unnecessary loops or computations
- N+1 queries
- Memory leaks
- Missing caching opportunities

**Maintainability**
- Code clarity and readability
- Proper naming conventions
- DRY principle violations
- Missing or unclear comments

**Testing**
- Test coverage for new code
- Edge cases tested
- Integration tests where needed

### 3. Provide Feedback

Use this format for each comment:

```
**[Category]** File:Line

Description of the issue or suggestion.

Suggested fix (if applicable):
\`\`\`
code example
\`\`\`
```

### 4. Summary

End with a summary:
- Overall assessment (Approve/Request Changes/Comment)
- Key strengths of the PR
- Critical issues that must be addressed
- Nice-to-have improvements

## Tone Guidelines

- Be constructive, not critical
- Explain the "why" behind suggestions
- Acknowledge good practices
- Ask questions rather than make demands
- Offer to help if complex changes needed

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.