qa-strategy-and-metrics
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"
What this skill does
# QA Strategy and Metrics Skill
## Metadata (Tier 1)
**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.
---
## Instructions (Tier 2)
### Testing Pyramid
```
E2E (5-10%)
Integration (15-20%)
Unit Tests (70-80%)
```
**Rationale**:
- **Unit**: Fast (ms), cheap, high confidence in individual components
- **Integration**: Moderate speed (seconds), tests component interactions
- **E2E**: Slow (seconds-minutes), expensive, fragile, but validates real workflows
**Anti-Pattern**: Inverted pyramid (too many E2E tests)
- Slow CI/CD pipeline
- Flaky tests due to external dependencies
- High maintenance burden
### Cyclomatic Complexity (CC)
**Formula**: CC = E - N + 2P
- E = edges in control flow graph
- N = nodes
- P = connected components
**Interpretation**:
- 1-5: Low risk, straightforward logic
- 6-10: Moderate complexity, well-structured
- 11-20: Complex, consider refactoring
- 21+: Very complex, MUST refactor
**When to refactor**:
- Function has CC > 15
- Function has multiple responsibilities
- Difficult to write tests (need many mocks)
### Code Coverage Metrics
**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
- May miss edge cases
- May not test error handling
- May not validate business logic
**Focus Areas**:
- Error handlers (try/except, catch)
- Boundary conditions (null, empty, max)
- Complex conditionals
### Maintainability Index (MI)
**Formula** (simplified):
```
MI = 171 - 5.2 * ln(HV) - 0.23 * CC - 16.2 * ln(LOC)
```
- HV = Halstead Volume (code complexity)
- CC = Cyclomatic Complexity
- LOC = Lines of Code
**Ranges**:
- 85-100: Highly maintainable
- 65-84: Moderately maintainable
- 0-64: Difficult to maintain
### Technical Debt
**Formula**: Debt = (Cost to Fix) * (Impact if Not Fixed)
**Types**:
1. **Code Debt**: Poor structure, duplication
2. **Test Debt**: Low coverage, missing tests
3. **Documentation Debt**: Missing/outdated docs
4. **Architectural Debt**: Design constraints
**When to Pay Down**:
- High-traffic code paths
- Before major refactoring
- Security-sensitive areas
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.