From quality-tools
Testing pyramid, quality metrics, and technical debt management strategies. PROACTIVELY activate for: (1) Designing testing strategy, (2) Evaluating code quality metrics, (3) Managing technical debt, (4) Analyzing test coverage approaches, (5) Calculating complexity. Triggers: "testing strategy", "testing pyramid", "quality metrics", "technical debt", "cyclomatic complexity", "maintainability", "coverage principles"
How this skill is triggered — by the user, by Claude, or both
Slash command
/quality-tools:qa-strategy-and-metricsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Keywords**: strategy, testing pyramid, quality, metrics, technical debt, complexity, maintainability, coverage principles
Keywords: strategy, testing pyramid, quality, metrics, technical debt, complexity, maintainability, coverage principles
File Patterns: N/A (conceptual skill)
Modes: code_review, testing_frontend, testing_backend
Activation: Conceptual queries about testing strategy, quality metrics, or technical debt.
E2E (5-10%)
Integration (15-20%)
Unit Tests (70-80%)
Rationale:
Anti-Pattern: Inverted pyramid (too many E2E tests)
Formula: CC = E - N + 2P
Interpretation:
When to refactor:
Statement Coverage: % of code lines executed Branch Coverage: % of decision paths taken (if/else, switch) Function Coverage: % of functions called
Critical Insight: 100% coverage ≠ 100% tested
Focus Areas:
Formula (simplified):
MI = 171 - 5.2 * ln(HV) - 0.23 * CC - 16.2 * ln(LOC)
Ranges:
Formula: Debt = (Cost to Fix) * (Impact if Not Fixed)
Types:
When to Pay Down:
npx claudepluginhub agentient/vibekit --plugin quality-toolsAssess and design for maintainability. Evaluate code complexity, coupling, and testability. Use when evaluating codebase health or designing for long-term evolution.
Analyzes and prioritizes technical debt in code, architecture, testing, docs, and infra with metrics dashboard, ROI roadmaps, effort estimates, and prevention strategies.
Analyzes codebases to identify and prioritize technical debt across code, architecture, testing, documentation, and infrastructure.