Skip to content
Skill

code-review-skill

by awesome-skills

AI Summary

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement. Before diving into code, understand: 1. Read PR description and linked issue

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "code-review-skill" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/code-review-skill && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/code-review-skill/SKILL.md "https://raw.githubusercontent.com/awesome-skills/code-review-skill/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, performance reviews, checking code quality, finding bugs, giving feedback on code.

Code Review Skill

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

When to Use This Skill

• Reviewing pull requests and code changes • Establishing code review standards for teams • Mentoring junior developers through reviews • Conducting architecture reviews • Creating review checklists and guidelines • Improving team collaboration • Reducing code review cycle time • Maintaining code quality standards

1. The Review Mindset

Goals of Code Review: • Catch bugs and edge cases • Ensure code maintainability • Share knowledge across team • Enforce coding standards • Improve design and architecture • Build team culture Not the Goals: • Show off knowledge • Nitpick formatting (use linters) • Block progress unnecessarily • Rewrite to your preference

2. Effective Feedback

Good Feedback is: • Specific and actionable • Educational, not judgmental • Focused on the code, not the person • Balanced (praise good work too) • Prioritized (critical vs nice-to-have) `markdown ❌ Bad: "This is wrong." ✅ Good: "This could cause a race condition when multiple users access simultaneously. Consider using a mutex here." ❌ Bad: "Why didn't you use X pattern?" ✅ Good: "Have you considered the Repository pattern? It would make this easier to test. Here's an example: [link]" ❌ Bad: "Rename this variable." ✅ Good: "[nit] Consider userCount instead of uc for clarity. Not blocking if you prefer to keep it." `

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 2mo ago
● Active
Adoption1K+ stars on GitHub
2.2k ★ · Popular
DocsREADME + description
Well-documented

GitHub Signals

Stars2.2k
Forks225
Issues6
Updated2mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code