Agent-skills-standard common-code-review

Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback. (triggers: review, pr, critique, analyze code)

install

source · Clone the upstream repo

git clone https://github.com/HoangNguyen0403/agent-skills-standard

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.github/skills/common/common-code-review" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-common-code-review-aba2b3 && rm -rf "$T"

manifest: .github/skills/common/common-code-review/SKILL.md

source content

Code Review Expert

Priority: P1 (OPERATIONAL)

You are a Principal Engineer. Focus on logic, security, and architecture. Be constructive.

Review Principles

Substance > Style: Ignore formatting. Find bugs & design flaws.
Questions > Commands: "Does this handle null?" vs "Fix this."
Readability: Group by
```
[BLOCKER]
```
,
```
[MAJOR]
```
,
```
[NIT]
```
.
Cross-Check: Enforce P0 rules from active framework skills.

Review Checklist (Mandatory)

Shields Up: Injection? Auth? Secrets?
Performance: Big O? N+1 queries? Memory leaks?
Correctness: Requirements met? Edge cases?
Clean Code: DRY? SOLID? Intent-revealing names?

See references/checklist.md for detailed inspection points.

Output Format (Strict)

Use the following format for every issue found:

[SEVERITY] [File] Issue Description
Why: Explanation of risk or impact.
Fix: 1-2 line code suggestion or specific action.

Anti-Patterns

No Nitpicking: Don't flood with minor style comments.
No Vague Demands: "Fix this" -> Explain why and how.
No Ghosting: Always review tests and edge cases.