| name | code-quality-review |
| description | Run a maintainability and structure review focused on abstraction quality, branching complexity, file growth, canonical ownership, duplication, and refactoring opportunities. Use when the user asks for code quality review, maintainability review, 代码质量审查, 可维护性审查, or comments about whether the change stays easy to understand, modify, test, and extend, including layering and ownership of the change / 改动的分层与归属. Not for generic PR review or independent diff review hunting regressions, concurrency, or test gaps; not for full-spectrum or 全维度代码审计; not for system architecture audits; not for applying refactors; not for pure security, formatting-only, or performance profiling. |
| category | development-workflows |
| tags | ["code-review","code-quality","maintainability","architecture","refactoring"] |
| version | 0.3.0 |
| argument-hint | [path-pr-or-diff] |
| allowed-tools | Read, Glob, Grep, Bash, Write |
Code Quality Review
Purpose
Use this skill to perform a strict, evidence-based review of code quality and maintainability. Focus on whether the change keeps the codebase easier to understand, modify, test, and extend.
Prioritize structural concerns over style nits: abstraction quality, branching complexity, file growth, boundary cleanliness, canonical-layer ownership, duplication, orchestration complexity, and refactoring opportunities that preserve behavior while simplifying the implementation.
When to Use
Use this skill when the user asks for:
code quality review, code review focused on quality/maintainability, or maintainability review- Comments about whether the change stays easy to understand, modify, test, and extend, including layering and ownership of the change (
改动的分层与归属)
- Chinese requests such as
代码质量审查, 代码质量 review, 可维护性审查, or 改动的分层与归属
When to Skip
Do not use this skill as the primary guide for:
- Generic PR review, independent git-diff review, or hunts for functional regressions, missed scenarios, wrong assumptions, concurrency, or test gaps — use
code-auditor (pr / dir)
- Full-spectrum or
全维度代码审计 — use code-auditor project
- System architecture audits
- Applying refactors or editing product code — use
code-refactor
- Related updates that can leave half-applied state — that is a correctness finding for
code-auditor
- Pure security audits, unless the user also asks about maintainability or code quality
- Performance profiling or benchmark-driven optimization
- Formatting-only, lint-only, or naming-only review
This skill is the focused structural and maintainability lens. Keep it for judging whether the change keeps the code easy to understand, modify, test, and extend.
Safety and Scope
- Treat the code under review as read-only. Never edit, reformat, refactor, commit, push, or run destructive git operations on it. The one exception is the opt-in artifact mode (see Output Modes), which only ever writes a review report under
code_review/ and never touches product code.
- Recommend concrete structural changes, but do not apply them. Hand off apply-refactor requests to
code-refactor.
