How do I install the Code Review skill?

Run npx skillmds@latest add asiaostrich/code-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Review?

AsiaOstrich (@asiaostrich) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Review by asiaostrich — Agent Skill

Name: Code Review
Rating: 4.2 (5 reviews)
Author: AsiaOstrich

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, 程式碼審查, 審查類別, 評論前綴.

AsiaOstrich e573a23 4 files · 21.5 KB Updated Sep 10, 2026

File contents

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.

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

Review Categories | 審查類別

Functionality - Does it work correctly? | 功能是否正確？
Design - Is the architecture appropriate? | 架構是否合適？
Quality - Is the code clean and maintainable? | 程式碼是否乾淨可維護？
Readability - Is it easy to understand? | 是否容易理解？
Tests - Is there adequate test coverage? | 測試覆蓋是否足夠？
Security - Are there any vulnerabilities? | 是否有安全漏洞？
Performance - Is it efficient? | 是否有效率？
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 — Read it before committing, as the pre-commit pass.
Detailed guide: guide.md
Core standard: code-review-checklist.md

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/code-review

For complete AI agent behavior definition, see the corresponding command file: /code-review

---name: code-reviewdescription: [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, 程式碼審查, 審查類別, 評論前綴.---# 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 systematically3. **Generate report** - Output findings with standard comment prefixes4. **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-代理行為)

Frequently asked questions