AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/code-review-assistant/SKILL.md

code-review

Skill4 starsChanged 28 days agoMITView on GitHub

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

195 other projects use a version of this.

Adopted by

Most recently taken up by

doggy8088/spec-kittheir own version, first seen Nov 9, 2026
strelov1/freehiretheir own version, first seen Nov 9, 2026
storybookjs/storybooktheir own version, first seen Nov 8, 2026
codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
supabase/supabasetheir own version, first seen Nov 8, 2026
The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

dzhngSkill
close-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
dzhngSkill
design-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
PydanticSkill
add-new-model
Add support for a newly-released language or image generation model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5, openai:gpt-image-2). Use when a provider ships a new model id and you need to wire literals, profile flags, adapters, and tests to recognize it. Handles SDK-lag, gateway list conventions, capability probing, and direct image-model geometry.
Also in 9 projects that use this
transitive-bullshitSkill
compare-screenshots
Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.
Also in 5 projects that use this
Microsoft AzureSkill
azsdk-common-apiview-feedback-resolution
Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.
Also in 6 projects that use this
Microsoft AzureSkill
azsdk-common-generate-sdk-locally
Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.
Also in 6 projects that use this
+4 more from dzhng
+2 more from Azure

Other versions195 projects use a version of this.
Word for word · 1
AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 194
mattpocock/skills★ 309ksame name
TheAlgorithms/Python★ 226ksame name
microsoft/vscode★ 195ksame name
github/spec-kit★ 149ksame name
ggml-org/llama.cpp★ 134ksame name
supabase/supabase★ 115ksame name
storybookjs/storybook★ 91ksame name
shareAI-lab/analysis_claude_code★ 80ksame name
shareAI-lab/learn-claude-code★ 80ksame name
vectorize-io/hindsight★ 60ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

0
Common
Most of the 184 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Apply checklist: - Check each review category systematically
line 42
Very specific:
After /code-review completes, the AI assistant should suggest:
line 75

“Common” is measured: kept by at least 6 in 10 of the 184 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

<!-- 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.

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free

Adopted by

Most recently taken up by

Used with

close-spec

design-with-images

add-new-model

compare-screenshots

azsdk-common-apiview-feedback-resolution

azsdk-common-generate-sdk-locally

Word for word · 1

Edited · 0

Wrote their own version · 194