Skill

analyze-pyramid

Analyzes test pyramid health by discovering, categorizing, and counting unit, integration, and E2E tests, then assesses distribution and recommends rebalancing.

Bash

.NET

testing

npx claudepluginhub melodic-software/claude-code-plugins --plugin test-strategy

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepBashSkillTask

Preview

Analyze the current test distribution and recommend improvements for a healthier test pyramid.

SKILL.md

Similar Skills

test-pyramid-design

Designs optimal test pyramids with unit/integration/E2E ratios. Identifies anti-patterns like ice cream cone, cupcake, hourglass and recommends architecture-specific strategies.

7 tools

test-strategy

Create testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.

2 files6 tools

testing

eng-testing

Provides language-agnostic test strategy guidelines: test pyramid (unit/integration/E2E), descriptive naming, mocking, flaky test policies. For writing tests, strategy design, coverage review.

jig

Stats

Parent Repo Stars63

Parent Repo Forks9

Last CommitFeb 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Analyze Test Pyramid Command

Analyze the current test distribution and recommend improvements for a healthier test pyramid.

Process

Step 1: Discover Tests

If a test directory is provided, use it. Otherwise, search for common test patterns:

# .NET projects
find . -name "*.Tests.csproj" -o -name "*Tests*.csproj"
find . -name "*Test*.cs" -type f

# Count tests
grep -r "\[Fact\]\|\[Theory\]" --include="*.cs" | wc -l

Step 2: Categorize Tests

Identify test levels by project/folder naming:

Unit: *.Unit.Tests, *.Domain.Tests
Integration: *.Integration.Tests, *.Api.Tests
E2E: *.E2E.Tests, *.Acceptance.Tests

Count tests at each level:

| Level | Project | Test Count |
|-------|---------|------------|
| Unit | MyApp.Domain.Tests | 150 |
| Unit | MyApp.Application.Tests | 80 |
| Integration | MyApp.Api.Tests | 60 |
| E2E | MyApp.E2E.Tests | 40 |

Step 3: Load Pyramid Skill

Invoke the test-strategy:test-pyramid-design skill for shape analysis patterns.

Step 4: Analyze Distribution

Calculate percentages and identify shape:

## Current Distribution

| Level | Count | Percentage | Target |
|-------|-------|------------|--------|
| Unit | 230 | 70% | 70% ✅ |
| Integration | 60 | 18% | 20% ✅ |
| E2E | 40 | 12% | 10% ⚠️ |

**Shape Assessment**: Near-healthy pyramid with slight E2E heaviness

Step 5: Identify Anti-Patterns

Check for common issues:

Ice Cream Cone: E2E > 30%
Hourglass: Integration > 50%
Inverted Pyramid: Unit < 50%
Missing Layer: Any level at 0%

Step 6: Generate Recommendations

Based on analysis:

## Recommendations

### Immediate Actions
1. **Reduce E2E tests** by 2% (8 tests)
   - Review for tests that can be pushed to integration level
   - Identify tests duplicating lower-level coverage

### Test Migration Candidates
| Current Level | Candidate | Recommended Level | Reason |
|---------------|-----------|-------------------|--------|
| E2E | Login validation | Integration | API test sufficient |
| E2E | Form validation | Unit | Pure logic test |
| Integration | Data transform | Unit | No I/O needed |

### Coverage Gaps
- Unit tests needed for: [business logic areas]
- Integration tests needed for: [API boundaries]

Step 7: Output Report

## Test Pyramid Analysis Complete

**Current Shape**: [Shape name]

**Distribution**:
```text

     ▲
    ███  E2E: 12%
   █████ Integration: 18%
  ███████ Unit: 70%

```

**Health Score**: [X/10]

**Key Findings**:
1. [Finding 1]
2. [Finding 2]

**Recommended Actions**:
1. [Action 1]
2. [Action 2]

Examples

Analyze current directory:

/test-strategy:analyze-pyramid

Specify test directory:

/test-strategy:analyze-pyramid tests/