skills/code-review-assistant/SKILL.md
[UDS] Perform systematic code review with checklist
npx skillsauth add asiaostrich/universal-dev-standards code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
⚠️ 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.
執行系統性的程式碼審查,使用標準化的檢查清單和評論前綴。
📖 以下為流程的參考結構,非可執行步驟;自動化/強制執行請用 adoption layer 工具鏈(XSPEC-095)。 The steps below are a reference structure, not an executable workflow.
git diff or git show| 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 | 僅供參考 |
/code-review - Review all changes in current branch/code-review src/auth.js - Review specific file/code-review feature/login - Review specific branchAfter /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/checkinquality gates- 僅有 💡 SUGGESTION → 執行
/commit提交變更 — Only suggestions → Run/commit- 審查中發現規範不實用或缺失 → 執行
/audit --report回報 — Found impractical or missing standards → Run/audit --report
完整的 AI 行為定義請參閱對應的命令文件:
/code-reviewFor complete AI agent behavior definition, see the corresponding command file:
/code-review
tools
[UDS] 從規格衍生 BDD 場景、TDD 骨架或 ATDD 表格
development
[UDS] /methodology: 選擇並追蹤開發方法論(SDD/BDD/TDD)。 Use when: 選擇方法論、切換開發模式、查詢當前方法論狀態。 若要查詢各階段對應指令請用 /dev-workflow。
testing
[UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables from specifications
development
[UDS] Create or review specification documents for Spec-Driven Development