review-code

仓库创建 2026年7月26日最近提交 19 小时前SkillHot 收录 15 小时前

这个 Skill 做什么

帮你有章法地看代码变更：先弄明白改动的意图再挑毛病，不只盯着 diff，还要读上下文并亲自验证改动和测试是否成立。适合在要 review pull request、diff 或分支时用，尤其改动范围大或设计复杂时更有价值。特别之处是把每个发现按严重性分类，并把意见按结构写好，避免只报风凉话。

▸ 展开 SKILL.md 英文原文

The repeatable process for reviewing a code change: understand the change's intent before critiquing, read the diff AND the surrounding code, verify the change's claims and tests rather than trusting them, categorize each finding by severity, and structure the written review. Load whenever the task is to review a pull request, diff, branch, or proposed code change - before you start reading the diff.

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/review-code/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/review-code/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Review code: understand → verify → categorize → structure

A good review improves the codebase's health - it is not a symptom scan of the diff. Reviewing lines in isolation misses the design flaw, trusts a test that never fails, and buries the one real bug under style nits. This process reviews the change the way it will actually be lived with.

Do not write a single finding until step 2: you cannot judge a change you don't yet understand.

## The workflow

### 1. Understand the intent and context first

Before looking critically at any line, learn what the change is *for*.

- Read the PR description / linked issue / commit messages. State in one sentence what problem this change claims to

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有