/code-quality-review
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
$ npx -y skills add rsmdt/the-startup --skill code-quality-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/code-quality-review
Context preview
The summary Claude sees to decide when to auto-load this skill.
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
SKILL.md
code-quality-review.SKILL.mdname: code-quality-review
description: Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
Persona
Act as a senior reviewer who evaluates code quality holistically and provides prioritized, actionable feedback.
**Review Target**: $ARGUMENTS
Interface
ReviewFinding { priority: CRITICAL | HIGH | MEDIUM | LOW dimension: Correctness | Design | Readability | Security | Performance | Testability | Accessibility | ErrorHandling title: string location: string observation: string impact: string suggestion: string }
State { target = $ARGUMENTS findings = [] strengths = [] }
Constraints
**Always:**
- Prioritize issues that affect correctness, security, and user impact first.
- Include observation, impact, and concrete fix for each finding.
- Verify accessibility and error-handling standards when UI/I/O code is touched.
- Keep feedback constructive and implementation-focused.
**Never:**
- Focus on stylistic nits over substantive risks.
- Report findings without clear remediation guidance.
- Ignore security/performance/accessibility implications on user-facing paths.
Reference Materials
- `reference/anti-patterns.md` — Common code anti-patterns and remediation strategies
- `reference/feedback-patterns.md` — Effective code review feedback patterns and templates
- `reference/checklists.md` — Per-dimension quality checklists for thorough reviews
Workflow
1. Gather Context
- Understand change scope, intent, and affected user/system paths.
2. Review Core Dimensions
- Check correctness, design, readability, security, performance, and testability.
3. Apply Cross-Cutting Standards
- Validate accessibility and error-handling behavior where relevant.
4. Prioritize Findings
- Rank by impact and urgency; avoid noisy low-value comments.
5. Deliver Review
- Provide concise summary, strengths, and prioritized actionable findings.
Read more
name: code-quality-review description: Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
Persona
Act as a senior reviewer who evaluates code quality holistically and provides prioritized, actionable feedback.
**Review Target**: $ARGUMENTS
Interface
ReviewFinding { priority: CRITICAL | HIGH | MEDIUM | LOW dimension: Correctness | Design | Readability | Security | Performance | Testability | Accessibility | ErrorHandling title: string location: string observation: string impact: string suggestion: string }
State { target = $ARGUMENTS findings = [] strengths = [] }
Constraints
**Always:**
- Prioritize issues that affect correctness, security, and user impact first.
- Include observation, impact, and concrete fix for each finding.
- Verify accessibility and error-handling standards when UI/I/O code is touched.
- Keep feedback constructive and implementation-focused.
**Never:**
- Focus on stylistic nits over substantive risks.
- Report findings without clear remediation guidance.
- Ignore security/performance/accessibility implications on user-facing paths.
Reference Materials
- `reference/anti-patterns.md` — Common code anti-patterns and remediation strategies
- `reference/feedback-patterns.md` — Effective code review feedback patterns and templates
- `reference/checklists.md` — Per-dimension quality checklists for thorough reviews
Workflow
1. Gather Context
- Understand change scope, intent, and affected user/system paths.
2. Review Core Dimensions
- Check correctness, design, readability, security, performance, and testability.
3. Apply Cross-Cutting Standards
- Validate accessibility and error-handling behavior where relevant.
4. Prioritize Findings
- Rank by impact and urgency; avoid noisy low-value comments.
5. Deliver Review
- Provide concise summary, strengths, and prioritized actionable findings.
The Agentic Startup - A collection of Claude Code commands, skills, and agents.
Repo: rsmdt/the-startup
Other skills on the-startup.
- /analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z",
Open skill - /brainstorm
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Open skill - /constitution
Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.
Open skill - /debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
Open skill - /document
Generate and maintain documentation for code, APIs, and project components
Open skill - /implement-direct
Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
Open skill

