Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
awesome-skills avatar

Code Review Skill

awesome-skills/code-review-skill

  • 890 installs
  • 1.6k repo stars
  • Updated July 16, 2026
  • awesome-skills/code-review-skill

Code Review Skill is an agent skill that guides constructive, multi-stack pull request and architecture reviews.

About

Code Review Skill is an agent skill that turns ad-hoc PR comments into a systematic, constructive review workflow for solo builders and small teams who wear the senior reviewer hat. It covers a wide surface of frameworks and languages—from React and Vue through Rust, Django, NestJS, and mobile stacks—so one install can support polyglot repos typical of indie SaaS. Invoke it when reviewing pull requests, drafting team standards, mentoring through feedback, or running architecture and security-flavored reviews before merge. The skill stresses catching bugs and edge cases, maintainability, and design improvement while explicitly avoiding format nitpicks that belong in linters. For Prism, canonical placement is Ship → Review with natural spill into Ship → Security when audits are requested. It complements stack-specific perf skills but does not replace automated CI; Bash access is intended to run lint, test, and build verification when the agent environment allows.

  • Review guidance spanning React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Python, Go, .NET, and more
  • Emphasizes knowledge sharing over gatekeeping with explicit review goals and anti-goals
  • Supports architecture reviews, mentoring juniors, and team review standards
  • Allowed tools include Read, Grep, Glob, Bash, and WebFetch for lint/test/doc verification
  • Use cases include security-oriented review passes and reducing review cycle time

Code Review Skill by the numbers

  • 890 all-time installs (skills.sh)
  • +192 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #165 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/awesome-skills/code-review-skill --skill code-review-skill

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs890
repo stars★ 1.6k
Security audit3 / 3 scanners passed
Last updatedJuly 16, 2026
Repositoryawesome-skills/code-review-skill ↗

What it does

Run structured, constructive PR and architecture reviews across many stacks when you are the only senior reviewer on the team.

Who is it for?

Best when you review every change yourself across multiple languages and want a repeatable review mindset plus checklist depth.

Skip if: Replacing automated formatters/linters or deep exclusive audits that need a dedicated security-only skill with no breadth tradeoff.

When should I use this skill?

Reviewing pull requests, conducting PR reviews, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, or giving feedback

What you get

You deliver structured review comments, validated quality checks when tools are available, and shared standards that improve code before it ships.

  • Structured review comments with bugs, design, and maintainability notes
  • Suggested follow-ups and standards aligned to review goals

By the numbers

  • Covers 15+ language and framework stacks including React 19, Vue 3, Angular 17+, and Svelte 5

Files

SKILL.mdMarkdownGitHub ↗

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

Core Principles

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)
❌ 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."

3. Review Scope

What to Review:

  • Logic correctness and edge cases
  • Security vulnerabilities
  • Performance implications
  • Test coverage and quality
  • Error handling
  • Documentation and comments
  • API design and naming
  • Architectural fit

What Not to Review Manually:

  • Code formatting (use Prettier, Black, etc.)
  • Import organization
  • Linting violations
  • Simple typos

Review Process

Phase 1: Context Gathering (2-3 minutes)

Before diving into code, understand: 1. Read PR description and linked issue 2. Check PR size (>400 lines? Ask to split) 3. Review CI/CD status (tests passing?) 4. Understand the business requirement 5. Note any relevant architectural decisions

For large diffs, pipe the diff through `scripts/pr-analyzer.py` (git diff main...HEAD | python scripts/pr-analyzer.py) to triage complexity and get a suggested review approach before reading.

Phase 2: High-Level Review (5-10 minutes)

1. Architecture & Design - Does the solution fit the problem?

  • For significant changes, consult Architecture Review Guide
  • Check: SOLID principles, coupling/cohesion, anti-patterns

2. Performance Assessment - Are there performance concerns?

  • For performance-critical code, consult Performance Review Guide
  • Check: Algorithm complexity, N+1 queries, memory usage

3. File Organization - Are new files in the right places? 4. Testing Strategy - Are there tests covering edge cases?

Phase 3: Line-by-Line Review (10-20 minutes)

For each file, check:

  • Logic & Correctness - Edge cases, off-by-one, null checks, race conditions
  • Security - Input validation, injection risks, XSS, sensitive data
  • Performance - N+1 queries, unnecessary loops, memory leaks
  • Maintainability - Clear names, single responsibility, comments
  • Reuse - Before accepting new code, search for existing utilities/helpers that could replace it. Check adjacent files and shared modules for similar patterns. See Universal Quality Guide for anti-patterns like parameter sprawl, leaky abstractions, nested conditionals, stringly-typed code, TOCTOU, and no-op updates.

Phase 4: Summary & Decision (2-3 minutes)

1. Summarize key concerns 2. Highlight what you liked 3. Make clear decision:

  • ✅ Approve
  • 💬 Comment (minor suggestions)
  • 🔄 Request Changes (must address)

4. Offer to pair if complex

Review Techniques

Technique 1: The Checklist Method

Use checklists for consistent reviews. See Security Review Guide for comprehensive security checklist.

Technique 2: The Question Approach

Instead of stating problems, ask questions:

❌ "This will fail if the list is empty."
✅ "What happens if `items` is an empty array?"

❌ "You need error handling here."
✅ "How should this behave if the API call fails?"

Technique 3: Suggest, Don't Command

Use collaborative language:

❌ "You must change this to use async/await"
✅ "Suggestion: async/await might make this more readable. What do you think?"

❌ "Extract this into a function"
✅ "This logic appears in 3 places. Would it make sense to extract it?"

Technique 4: Differentiate Severity

Use labels to indicate priority:

  • 🔴 [blocking] - Must fix before merge
  • 🟡 [important] - Should fix, discuss if disagree
  • 🟢 [nit] - Nice to have, not blocking
  • 💡 [suggestion] - Alternative approach to consider
  • 📚 [learning] - Educational comment, no action needed
  • 🎉 [praise] - Good work, keep it up!

Severity levels: 🔴 / 🟡 / 🟢 are the three severity tiers used as the standard across all guides in this skill — 🔴 blocks the merge, 🟡 should be addressed, 🟢 is optional. The remaining markers (💡 / 📚 / 🎉) are non-blocking annotations.

Language-Specific Guides

根据审查的代码语言，查阅对应的详细指南：

Language/FrameworkReference FileKey Topics
ReactReact GuideHooks, useEffect, React 19 Actions, RSC, Suspense, TanStack Query v5
Vue 3Vue GuideComposition API, 响应性系统, Props/Emits, Watchers, Composables
Angular 17+Angular GuideSignals, Standalone 组件, RxJS, Zoneless 变更检测, 模板优化
RustRust Guide所有权/借用, Unsafe 审查, 异步代码, 取消安全性, 错误处理
TypeScriptTypeScript Guide类型安全, async/await, 不可变性
PythonPython Guide可变默认参数, 异常处理, 类属性
Django / DRFDjango Guide安全审查, N+1 查询, Serializer 反模式, ViewSet, 异步视图
FastAPIFastAPI GuideDepends, Pydantic v2 validation, async correctness, sessions/N+1, auth vs authorization, test-driven verification
JavaJava GuideJava 17/21 新特性, Spring Boot 3, 虚拟线程, Stream/Optional
PHPPHP GuidePHP 8.x type system, PDO, security review, Composer, PHPUnit/PHPStan
C# / .NETC# GuideC# 12 特性, 异步编程, EF Core 性能, ASP.NET Core, LINQ
GoGo Guide错误处理, goroutine/channel, context, 接口设计
Kotlin / AndroidKotlin Guide协程, Flow, Jetpack Compose, 空安全, 内存泄漏, 架构模式
Swift / SwiftUISwift GuideOptionals, Swift Concurrency, Sendable/actors, SwiftUI property wrappers, value vs reference types, API design
NestJSNestJS Guide依赖注入, 分层架构, DTO 验证, Guard/Interceptor, 循环依赖
Svelte / SvelteKitSvelte GuideRunes, Load 函数, Form Actions, Store 迁移, SSR/CSR 边界
CC Guide指针/缓冲区, 内存安全, UB, 错误处理
C++C++ GuideRAII, 生命周期, Rule of 0/3/5, 异常安全
CSS/Less/SassCSS Guide变量规范, !important, 性能优化, 响应式, 兼容性
QtQt Guide对象模型, 信号/槽, 内存管理, 线程安全, 性能

Cross-Cutting Guides

Language-agnostic patterns applicable to all code reviews:

TopicReference FileKey Topics
Universal QualityUniversal Quality GuideReuse audit, parameter sprawl, leaky abstractions, nested conditionals, stringly-typed code, TOCTOU, no-op updates, redundant state

Additional Resources

  • Architecture Review Guide - 架构设计审查指南（SOLID、反模式、耦合度）
  • Performance Review Guide - 性能审查指南（Web Vitals、N+1、复杂度）
  • Common Bugs Checklist - 按语言分类的常见错误清单
  • Security Review Guide - 安全审查指南
  • Code Review Best Practices - 代码审查最佳实践
  • PR Review Template - PR 审查评论模板
  • Review Checklist - 快速参考清单

Related skills

mattpocockImprove Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196kjuliusbrusseeCaveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kmattpocockCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kjuliusbrusseeCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kmattpocockCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196kobraRequesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264k

How it compares

Broad multi-framework review playbook—pair with stack-specific checkers like React perf rules instead of one-size-fits-all static analysis.

FAQ

Who is code-review-skill for?

Developers conducting PR reviews, mentoring others, or setting team review culture—especially solos who lack a dedicated review committee.

When should I use code-review-skill?

At Ship → review on every meaningful PR, during architecture discussions in Build, or for security-flavored passes in Ship → security before release.

Is code-review-skill safe to install?

It may invoke Bash and network fetches to verify quality; review the Security Audits panel on this Prism page and restrict tools in untrusted repos.

Code Review & Qualitygittestingbackend
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.