Agent skill

Code Review Skill

by Rain-kl in Rain-kl/OpenFlare

Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more.

MITAuto-check: notesDevelopment

Install Code Review Skill

skills CLI
$ npx skills add Rain-kl/OpenFlare --skill code-review-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Rain-kl/OpenFlare code-review-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Rain-kl/OpenFlare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-review-skill .claude/skills/code-review-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review-skill
GitHub stars
288
Token cost
~2.3k tokens
SKILL.md length
830 words
Files
39 (incl. scripts, assets)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more.

  • Works in 7 steps: The Review Mindset → Effective Feedback → Review Scope → …
  • : reviewing pull requests
  • SKILL.md covers When to Use This Skill, Core Principles, Review Process and Review Techniques, plus 3 more sections
  • Calls git and python

What it does

Code Review Skill is an agent skill from Rain-kl/OpenFlare. Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 40 other files, including scripts and assets (for example `CONTRIBUTING.md`, `README.md` and `assets/pr-review-template.md`).

It sits in Development, covering Pull requests, Code review and Software architecture. It works with Python, Angular, Django and NestJS. The repository describes itself as: OpenFlare is an open-source CDN orchestration and edge security platform. It supports reverse proxy, centralized configuration synchronization, in-network tunneling (Tunnels)… The licence is MIT.

When your agent uses it

  • : reviewing pull requests
  • Conducting PR reviews
  • Reviewing code changes
  • Establishing review standards

Example prompts

  • “Use the code-review-skill skill to provide comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java…”
  • “/code-review-skill”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, WebFetch

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. The Review Mindset
  2. Effective Feedback
  3. Review Scope
  4. Context Gathering (2-3 minutes)
  5. High-Level Review (5-10 minutes)
  6. Line-by-Line Review (10-20 minutes)
  7. Summary & Decision (2-3 minutes)

What it can do on your machine

Read from SKILL.md and the folder at commit 7483897. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Review Skill loads about 2.3k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 830 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~131
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, WebFetch

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from Rain-kl/OpenFlare at commit 7483897, republished under its MIT licence (© Rain-kl). 830 words, ~2,349 tokens.

Download SKILL.mdSave it as .claude/skills/code-review-skill/SKILL.md (or your agent's skills folder). This skill also uses 38 other files; get the full folder from GitHub.
name
code-review-skill
description
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C#/.NET, Kotlin, Swift, NestJS, C/C++, and more. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.
allowed-tools
Read, Grep, Glob, Bash, WebFetch

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)
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."
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?
  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:

markdown
❌ "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:

markdown
❌ "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?"
Show full SKILL.md (355 more words)Show less
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

© Rain-kl, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 38 other files (scripts, assets) in .agents/skills/code-review-skill of Rain-kl/OpenFlare.

  • SKILL.md
  • .gitignore
  • .nojekyll
  • CONTRIBUTING.md
  • LICENSE
  • README.md
  • assets/pr-review-template.md
  • assets/review-checklist.md
  • index.en.html
  • index.html
  • reference/angular.md
  • reference/architecture-review-guide.md
  • reference/c.md
  • reference/code-quality-universal.md
  • reference/code-review-best-practices.md
  • reference/common-bugs-checklist.md
  • reference/cpp.md
  • reference/csharp.md
  • reference/css-less-sass.md
  • … and 20 more

Open the folder on GitHubat commit 7483897

Compare with similar skills

Code Review Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Review Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Review Skill this skillRain-kl/OpenFlare288—~2.3kAutomated safety check: NotesMIT
Code Review Skillawesome-skills/code-review-skill2.1k—~2.8kAutomated safety check: NotesMIT
Code Review Excellenceandrew-yangy/gru-ai155—~1.7kAutomated safety check: NotesMIT
Code Reviewerjewbetcha/opentrace1162 repos~1.1kAutomated safety check: NotesMIT
Code Revieweralirezarezvani/claude-skills28k1 repos~1.6kAutomated safety check: PassMIT
Code Reviewerborghei/Claude-Skills874—~1.7kAutomated safety check: PassMIT

Similar skills

  • Code Review Skill

    awesome-skills/code-review-skill

    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…

    2.1k GitHub stars~2.8k tokensUpdated 29 days ago
    DevelopmentAuto-check: notes
  • Code Review Excellence

    andrew-yangy/gru-ai

    Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.

    155 GitHub stars~1.7k tokensUpdated 7 mo ago
    DevelopmentAuto-check: notes
  • Code Reviewer

    jewbetcha/opentrace

    Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.

    116 GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check: notes
  • Code Reviewer

    alirezarezvani/claude-skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Code Reviewer

    borghei/Claude-Skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, and Kotlin.

    874 GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Senior Fullstack

    borghei/Claude-Skills

    Fullstack development toolkit with project scaffolding for Next.js/FastAPI/MERN/Django stacks and code quality analysis.

    874 GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

More from Rain-kl/OpenFlare

All 12 skills in this repo
  • Go Logging

    Rain-kl/OpenFlare

    在选择日志方案、配置 slog、编写结构化日志语句或决定日志级别时使用。也适用于设置生产日志、为日志添加请求作用域上下文或从 log 迁移到 slog 的场景,即使用户未明确提及日志。不涵盖错误处理策略(参见 go-error-handling)。

    288 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • New API

    Rain-kl/OpenFlare

    Wavelet 项目专用:当新增或修改自定义业务 API、新增业务路由、新增 service 层核心逻辑时必须使用。本技能指导包职责划分、推荐文件结构、路由解耦、Swagger 文档生成与质量门禁验证。

    288 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Cache Framework

    Rain-kl/OpenFlare

    Wavelet 项目专用:当新增或修改业务缓存(RAM/Redis/DB 三层读路径)、缓存失效、多节点 pub/sub 同步、或评估高频读是否应接入缓存时必须使用。本技能说明系统标准缓存框架、参考实现、禁止写法与分布式一致性要求。

    288 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Clickhouse Batchwriter

    Rain-kl/OpenFlare

    Wavelet 项目专用:当新增或修改 ClickHouse 批量写入、接入 internal/infra/persistence/batchwriter、将业务域异步 flush 到分析表、迁移 riskcontrol/节点访问日志/可观测时序写入、或评估 asyncinsert 与背压策略时必须使用。本技能指导分层职责、各域独立 Writer 实例、repository 批量 API…

    288 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Database Migration

    Rain-kl/OpenFlare

    Wavelet 项目专用:当新增或修改数据库表结构、索引、初始化数据、系统配置 seed、模板 seed、默认管理员、goose SQL 迁移、internal/infra/persistence/migrator、ClickHouse 分析库 DDL 或数据库升级流程时必须使用。本技能指导在 internal/infra/persistence/migrator/goose 下编写…

    288 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • File Upload

    Rain-kl/OpenFlare

    Wavelet 项目专用:当业务需要上传文件、读取已上传文件、在 Worker/任务中程序化摄取字节流、选择存储引擎能力、或排查 wuploads / 文件统计异常时必须使用。本技能指导 storage 与 upload 分层、upload.Ingest 策略选型、前后端接入与禁止旁路写表。

    288 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Code Review Skill

What does Code Review Skill do?

Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more. Code Review Skill is an agent skill from Rain-kl/OpenFlare.NET, Kotlin, Swift, NestJS, C/C++, and more.

When should I use Code Review Skill?

Code Review Skill fits situations like: : reviewing pull requests; conducting PR reviews; reviewing code changes; establishing review standards.

How do I install Code Review Skill in Claude Code?

Run `npx skills add Rain-kl/OpenFlare --skill code-review-skill -a claude-code`. Or copy the skill folder (.agents/skills/code-review-skill in Rain-kl/OpenFlare) into .claude/skills/code-review-skill in your project. Claude Code loads it when a task matches its description.

How do I install Code Review Skill in Codex?

Run `npx skills add Rain-kl/OpenFlare --skill code-review-skill -a codex`. Or copy the skill folder (.agents/skills/code-review-skill in Rain-kl/OpenFlare) into .agents/skills/code-review-skill in your project. Codex loads it when a task matches its description.

Can I use Code Review Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Rain-kl/OpenFlare --skill code-review-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review-skill, .gemini/skills/code-review-skill, .github/skills/code-review-skill and .opencode/skills/code-review-skill in your project.

What does Code Review Skill need to run?

Going by SKILL.md and its folder, Code Review Skill needs the command-line tools its instructions call (git and python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, WebFetch.

Does Code Review Skill access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Code Review Skill safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Code Review Skill use?

Code Review Skill is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Review Skill use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Review Skill?

Skills that share tags, products or a category with Code Review Skill: Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Code Review Excellence (andrew-yangy/gru-ai, 155 stars), Code Reviewer (jewbetcha/opentrace, 116 stars) and Code Reviewer (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review Skill?

Rain-kl (a GitHub user) maintains it in Rain-kl/OpenFlare, which has 288 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: Rain-kl/OpenFlare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.