Skip to content
Skills Library
Programming · Learning & explanation

code-review

/code-review

[UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes. Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team. Not for: executing a gated review workflow — that moved to the adoption layer (XSPEC-095); pre-commit gate verification — use /checkin. Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 程式碼審查, 審查類別, 評論前綴.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

[UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes. Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team. Not for: executing a gated review workflow — that moved to the adoption layer (XSPEC-095); pre-commit gate verification — use /checkin. Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 程式碼審查, 審查類別, 評論前綴.

Arguments

/code-review [file path or branch | 檔案路徑或分支名稱]
Original author description

[UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes. Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team. Not for: executing a gated review workflow — that moved to the adoption layer (XSPEC-095); pre-commit gate verification — use /checkin. Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 程式碼審查, 審查類別, 評論前綴.

How it works

  1. Workflow | 工作流程
  2. Review Categories | 審查類別
  3. Comment Prefixes | 評論前綴
  4. Usage | 使用方式
  5. Next Steps Guidance | 下一步引導
  6. Reference | 參考
  7. AI Agent Behavior | AI 代理行為
Original SKILL.md headings · 76 lines, 472 words
SKILL.md preview
---
name: code-review
scope: universal
description: |
  [UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes.
  Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team.
  Not for: executing a gated review workflow — that moved to the adoption layer (XSPEC-095); pre-commit gate verification — use /checkin.
  Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 程式碼審查, 審查類別, 評論前綴.
allowed-tools: Read, Grep, Glob, Bash(git diff:*), Bash(git log:*), Bash(git show:*)
argument-hint: "[file path or branch | 檔案路徑或分支名稱]"
status: reference
# 2026-08-17: `disable-model-invocation: true` removed. It was applied by d415937e
# alongside the description rewrite, and followed no stateable rule — of the six
# skills carrying `status: reference`, four (tdd, bdd, atdd, pr-automation) were
# never disabled despite the identical XSPEC-095 relocation. Same category,
# opposite treatment. The rule is now stateable: a reference is model-invocable.
# pr-automation-assistant routes "the substance of the review itself" to
# /code-review, and that referral was unreachable while this flag was set.
---
<!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
  Code review workflow orchestration (4-step sequence, outcome gating) relocated to adoption layer
  (XSPEC-095, 2026-04-28). This Skill retains: 8 review category definitions,
  BLOCKING/IMPORTANT/SUGGESTION/QUESTION/NOTE prefix semantics.
  For enforced execution, use your adoption layer's toolchain.
-->

# Code Review Assistant | 程式碼審查助手

> ⚠️ **Status: Reference(參考用,非可執行流程)** — 程式碼審查流程協調(4 步驟序列、outcome gating)已於 2026-04-28 移至 **adoption layer(XSPEC-095)**。此處保留 8 大審查類別定義、BLOCKING/IMPORTANT/SUGGESTION/QUESTION/NOTE 前綴語意供參考。
> Lifecycle orchestration has moved to the adoption layer (XSPEC-095); this document is **reference-only**. For enforced execution, use your adoption layer's toolchain.

Perform systematic code review using standardized checklists and comment prefixes.

執行系統性的程式碼審查,使用標準化的檢查清單和評論前綴。

## Workflow | 工作流程

> 📖 以下為流程的**參考結構**,非可執行步驟;自動化/強制執行請用 adoption layer 工具鏈(XSPEC-095)。
> The steps below are a **reference structure**, not an executable workflow.

1. **Identify changes** - Get diff of files to review via `git diff` or `git show`
2. **Apply checklist** - Check each review category systematically
3. **Generate report** - Output findings with standard comment prefixes
4. **Summarize** - Provide overall assessment and recommended actions

## Review Categories | 審查類別

1. **Functionality** - Does it work correctly? | 功能是否正確?
2. **Design** - Is the architecture appropriate? | 架構是否合適?
3. **Quality** - Is the code clean and maintainable? | 程式碼是否乾淨可維護?
4. **Readability** - Is it easy to understand? | 是否容易理解?
5. **Tests** - Is there adequate test coverage? | 測試覆蓋是否足夠?
6. **Security** - Are there any vulnerabilities? | 是否有安全漏洞?
7. **Performance** - Is it efficient? | 是否有效率?
8. **Error Handling** - Are errors handled properly? | 錯誤處理是否妥當?

## Comment Prefixes | 評論前綴

| Prefix | Meaning | Action | 動作 |
|--------|---------|--------|------|
| **BLOCKING** | Must fix before merge | Required | 必須修復 |
| **IMPORTANT** | Should fix | Recommended | 建議修復 |
| **SUGGESTION** | Nice-to-have | Optional | 可選改善 |
| **QUESTION** | Need clarification | Discuss | 需要討論 |
| **NOTE** | Informational | FYI | 僅供參考 |

## Usage | 使用方式

- `/code-review` - Review all changes in current branch
- `/code-review src/auth.js` - Review specific file
- `/code-review feature/login` - Review specific branch

## Next Steps Guidance | 下一步引導

After `/code-review` completes, the AI assistant should suggest:

> **程式碼審查完成。建議下一步 / Code review complete. Suggested next steps:**
> - 有 ❗ BLOCKING 項目 → 修復後重新執行 `/code-review` — Fix issues then re-run `/code-review`
> - 全部通過 → 執行 `/checkin` 品質關卡 ⭐ **Recommended / 推薦** — All passed → Run `/checkin` quality gates
> - 僅有 💡 SUGGESTION → 執行 `/commit` 提交變更 — Only suggestions → Run `/commit`
> - 審查中發現規範不實用或缺失 → 執行 `/audit --report` 回報 — Found impractical or missing standards → Run `/audit --report`

## Reference | 參考

- [Pre-Commit Checklist](./checkin-checklist.md) — Read it before committing, as the pre-commit pass.
- Detailed guide: [guide.md](./guide.md)
- Core standard: [code-review-checklist.md](../../core/code-review-checklist.md)


## AI Agent Behavior | AI 代理行為

> 完整的 AI 行為定義請參閱對應的命令文件:[`/code-review`](../commands/code-review.md#ai-agent-behavior--ai-代理行為)
>
> For complete AI agent behavior definition, see the corresponding command file: [`/code-review`](../commands/code-review.md#ai-agent-behavior--ai-代理行為)
Files in this package (4)
  • SKILL.md 5 KB
  • checkin-checklist.md 5 KB
  • guide.md 6 KB
  • review-checklist.md 5 KB

Versions

RepositoryScoreLicence
This page · AsiaOstrich/universal-dev-standards95MIT
microsoft/aspire100MIT
kdlbs/kandev100AGPL-3.0
dotnet/runtime100MIT
drosam/agents100MIT
ggml-org/llama.cpp100MIT
ShamelesAbyss/Nyx100Apache-2.0
dzhng/jevgrep100MIT
iuliandita/skills100MIT

Database snapshot: 13.11.2026 · package version 0330251f1e34 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90code-review-assistant
    [UDS] 系統性程式碼審查的參考資料:八大審查類別,以及 BLOCKING/IMPORTANT/SUGGESTION 評論前綴。 Use when: 審查 pull request 或 diff、決定審查意見的措辭與優先序、與團隊議定審查範圍。 Not for: 執行有關卡的審查流程——該部分已移至採用層(XSPEC-095);提交前的關卡驗證——請用 /checkin。 Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix,…
  • 100code-review-patterns
    Code review checklist, what to look for, how to give feedback, PR review flow. Use when reviewing a pull request, or when preparing code for review.
  • 100review-pr
    Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".
  • 100code-review-guide
    Use when writing, structuring, or labelling code-review feedback on a pull or merge request: Conventional Comments labels (praise / nitpick / suggestion / issue / question / thought / chore / todo), the blocking vs non-blocking vs if-minor decorations, pairing one top-level…
  • 100code-review-checklist
    A ten-category human code-review rubric — correctness, design, readability, testing, security, performance, documentation, dependencies, error handling, and style — plus process guidance on feedback tone, review size, and a pre-submit self-review pass. Use when a review verdict…
  • 100mr-comments
    Use when writing a merge request or pull request review finding, the review's summary note, or a reply on a review thread (from /mr-review or the mr-fix process). Severity labels, comment shape, suggestions, the summary format and the reply style. Platform-neutral; a repo's own…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.