Code Review
Performs a structured, comprehensive code review of git changes (uncommitted, staged, current branch vs base, a single commit, a commit range, or a GitHub pull request or GitLab merge request by number or URL). Detects the stack and architecture automatically, applies stack- and pattern-specific rules, and reports findings by severity. Use when the user runs /code-review or /review-pr, or asks to "review my changes", "review PR", "review this branch", "do a code review", "revisar minhas mudanças", "revisar o PR" or "fazer code review".
Install
npx skills add felipereisdev/code-review-skill --skill code-reviewgit clone --depth 1 https://github.com/felipereisdev/code-review-skill.git /tmp/code-review-skill
mkdir -p ~/.claude/skills
cp -r /tmp/code-review-skill/. ~/.claude/skills/code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review ## Step 0 — Scope Selection Choose the scope before anything else. Take it from the arguments when there are any, and detect it when there are none. Ask the user only in the interactive cases listed under **Interactive runs**. **Scopes.** Each scope is one plain word, followed by a value where shown: 1. **`uncommitted`** — staged and unstaged changes to tracked files, plus untracked files that are not ignored. Run `git diff HEAD`, then list the untracked files with `git status --porcelain --untracked-files=all` (the lines that start with `??`) and review each one as a new file. Skip binary files. Before the first commit, HEAD does not resolve: run `git diff --cached` and `git diff` instead of `git diff HEAD`, and review the untracked files the same way. 2. **`staged`** — changes added to the index but not committed. Run `git diff --cached`. 3. **`branch [<base>]`** — every commit on the current branch since it left `<base>`. Run `git diff <base>...HEAD`. Without `<base>`, use the default branch. 4. **`commit <sha>`** — the changes of one commit. Run `git show <sha>`. 5. **`range <from>..<to>`** — the changes between two commits. Run `git diff <from>..<to>`. 6. **`pr <number|url>`** — a GitHub pull request or GitLab merge request, by number or URL. Read it with `gh` or `glab` as **Pull Request Scope** describes, never with git alone; its diff is what `gh pr diff` or `glab mr diff` prints.
Details
- Skill name
code-review- Repository
- felipereisdev/code-review-skill
- License
- MIT
- Repo updated
- 28 October 2026
FAQ
What does the Code Review skill do?
Performs a structured, comprehensive code review of git changes (uncommitted, staged, current branch vs base, a single commit, a commit range, or a GitHub pull request or GitLab merge request by number or URL). Detects the stack and architecture automatically, applies stack- and pattern-specific rules, and reports findings by severity. Use when the user runs /code-review or /review-pr, or asks to "review my changes", "review PR", "review this branch", "do a code review", "revisar minhas mudanças", "revisar o PR" or "fazer code review".
How do I install the Code Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add felipereisdev/code-review-skill --skill code-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Review popular?
It lives in felipereisdev/code-review-skill, which has 30 GitHub stars and 3 forks.
Related skills
Add Skill Installer
28kevintsai1202/add-skill-installer
安裝 Agent Skills 到本機。當用戶想要「安裝技能」、「新增 skill」、「從 GitHub 安裝 skill」、或「install skill from repo」時觸發此技能。
Gitmoot
24gitmoot/gitmoot
Use Gitmoot for local-first AI agent coordination across repositories, reviews, GitHub PR comments, daemon jobs, stuck jobs, branch locks, agent templates, custom prompt agents, orchestration, heartbeats, pipelines, routing telemetry, event webhooks, the web dashboard, runtime metadata, and Codex, Claude Code, Kimi Code, or omp runtime workflows.
Rsshub Route Authoring Skill
27AboutRSS/rsshub-route-authoring-skill
Author PR-ready RSSHub routes — namespace.ts, route handler, Radar rules and PR description — that survive code review. Distilled from 2,727 route PRs. Use when asked to write, fix or review an RSSHub route, add an RSS feed for a website via RSSHub, contribute a route to DIYgod/RSSHub, or when working with cheerio selectors, cache.tryGet, parseDate, Radar rules, or the RSSHub PR template. Trigger on RSSHub, RSS route, RSS feed for X, 给 X 做 RSS 订阅, namespace.ts, DataItem. Do not use for deploying RSSHub, debugging runtime errors, tuning cache/config, or non-RSSHub scraping.
Parallel Agent Worktree Skill
33TheAhmadOsman/parallel-agent-worktree-skill
Plan and execute complex work with parallel CLI agent-harness workers in git worktrees. Use for task decomposition, tmux worker spawning, deterministic loops, integration, verification, changelogs, and cleanup.
Git Ship
20oil-oil/git-ship
自动化 Git 工作流一键发布助手,执行完整的「ship」流程: 基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。 调用 ship 本身就是对完整流程的授权;自动推断分支名、commit message 和 PR 内容, 并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败,持续修复和重试, 直到改动成功合并。不要因可自行修复的失败暂停,只在认证、权限、仓库保护等 无法由当前环境解决的外部阻塞出现时请求用户介入。 仅在用户明确表达「ship」意图时触发,例如: - 直接说「ship」「/ship」「git ship」 - 明确要求完整走完 git 流程:「帮我走一遍 git 流程」「拉 main、切分支、提 PR、合并」 - 使用类似「发布这次改动」「把这些改动提成 PR 并合并」的表达 不应触发的情况: - 只是想 commit - 只是想创建 PR - 只是想 push 代码 - 讨论 git 相关问题或解释 git 概念
Skill Publisher
41joeseesun/qiaomu-skill-publisher
一键发布 agent skill 到 GitHub,自动验证 SKILL.md、生成或检查更吸引人的 README、区分 skill name 与 GitHub repo name、创建或更新仓库、推送并通过 npx skills 真实安装验证。当用户说"发布这个skill"、"publish skill"、"把skill发到GitHub"、"分享这个skill"、"/publish-skill"时触发。支持发布当前目录或指定路径的 skill。
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.