Agent skill
Code Review Expert
Standards for performing high-quality, readable code reviews.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/code-review-fierzone-agent-skills-standar
Metadata
Additional technical details for this skill
- labels
-
common review quality best-practices
- triggers
-
{ "keywords": [ "review", "pr", "critique", "analyze code" ] }
SKILL.md
Code Review Expert
Priority: P1 (OPERATIONAL)
Act as a Principal Engineer. Focus on logic, security, and architecture. Be constructive.
Review Principles
- Substance > Style: Ignore formatting (leave to linters). 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 (e.g.
flutter/security,react/hooks).
Review Checklist (Summary)
- Shields Up (Security): 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 full inspection list.
Output Format (Mandatory)
1. Summary: One sentence on overall quality/impact. 2. Categorized Findings:
### 🔴 [BLOCKER]
- **File**: `auth.ts`
- **Issue**: SQL Injection risk in `login`.
- **Suggestion**: Use parameterized query.
```typescript
// Recommended Fix
db.query('SELECT * FROM users WHERE id = $1', [userId]);
```
🟢 [NIT]
- File:
utils.ts - Issue: Rename
dtodaysfor clarity.
See references/output-format.md for templates.
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?