AgentSkillsCN

quality

在 spaces/[project]/ 中进行全面的代码质量评估。在提交、合并或发布前使用，以确保代码质量始终如一。

SKILL.md
--- frontmatter
name: quality
description: "Comprehensive code quality assessment in spaces/[project]/. Use before commits, merges, or releases to ensure consistent quality."
model: claude-sonnet-4-20250514
allowed-tools: Read, Glob, Grep, Bash, Task

/quality

Comprehensive quality assessment of code using multi-agent analysis.

Usage

bash
/quality yourbench                  # Full assessment
/quality yourbench --focus security # Security-focused
/quality coordinatr --focus testing # Test coverage focus

Focus Areas

FlagAnalysisAgent
(none)All dimensionsAll specialists
--focus securityOWASP, vulnerabilitiessecurity-auditor
--focus performanceBottlenecks, N+1performance-optimizer
--focus testingCoverage, test qualitytest-engineer
--focus codeMaintainabilitycode-reviewer

Execution Flow

1. Locate Project

bash
ls spaces/[project]/

2. Run Automated Checks

bash
cd spaces/[project]
npm test -- --coverage
npm run lint
npm run type-check  # if TypeScript

3. Agent Analysis

Coordinate specialists via Task tool:

  • •code-reviewer: Complexity, best practices
  • •security-auditor: OWASP Top 10
  • •performance-optimizer: N+1 queries, bottlenecks
  • •test-engineer: Coverage, test quality

4. Generate Report

markdown
## Quality Assessment: [project]

**Overall Score: XX/100** [status]

### Code Quality: XX/100
- Issues found
- Recommendations

### Security: XX/100
- Critical/High/Medium issues
- Recommendations

### Performance: XX/100
- Bottlenecks identified
- Recommendations

### Testing: XX/100
- Coverage percentage
- Untested areas

### Priority Actions
1. **CRITICAL**: [action]
2. **HIGH**: [action]
3. **MEDIUM**: [action]

Scoring

ScoreStatusMeaning
90-100ExcellentShip it
80-89GoodMinor improvements
70-79AcceptableAddress soon
60-69ConcerningFix before merge
<60CriticalMust fix

Quality Dimensions

Code Quality

  • •Cyclomatic complexity
  • •Code duplication
  • •SOLID principles
  • •Dead code detection

Security

  • •OWASP Top 10
  • •Auth/authz patterns
  • •Input validation
  • •Secrets in code

Performance

  • •N+1 query detection
  • •Inefficient algorithms
  • •Bundle size
  • •Caching opportunities

Testing

  • •Line/branch coverage
  • •Test quality
  • •Edge case coverage
  • •Integration test gaps

When to Use

  • •Before major release
  • •Onboarding to new codebase
  • •Periodic health checks
  • •Before refactoring