skills.rest
samuelfaj
samuelfajCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-test-coverage

Analyze code diffs and generate a layered test coverage matrix.

1|Updated May 1, 2026
Search Tags:#test-coverage#risk-based#testing-strategy#qa-automation#exhaustive#branch-diff#coverage-matrix
One-click install
npx skills add https://github.com/samuelfaj/sam-skills --skill create-test-coverage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-test-coverage
Source: https://github.com/samuelfaj/sam-skills/tree/main/create-test-coverage
Command: npx skills add https://github.com/samuelfaj/sam-skills --skill create-test-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure comprehensive test coverage by analyzing changes and proposing the smallest reliable test layer for maximum confidence across unit, integration, API/contract, and E2E tests.

Core Features & Use Cases

  • Build a coverage matrix for affected behaviors and generate a plan mapping to unit, integration, API/contract, and E2E tests.
  • Inspect diffs, assess risks, and propose test scopes and strategies for backend or frontend changes.
  • Use Case: When a feature touches multiple layers, automatically plan a layered test approach and report confidence blockers.

Quick Start

Provide a testing strategy by analyzing the current branch diff and generating a layered coverage plan.

Frequently Asked Questions about create-test-coverage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a risk-based test coverage plan for a branch diff?▼

To generate risk-based test coverage, you can analyze the branch diff to identify affected behaviors and map them to the smallest reliable test layer, producing a layered coverage matrix for unit, integration, API, and E2E tests.

What is the best way to map exhaustive test coverage across multiple application layers?▼

Exhaustive test coverage across layers is achieved by inspecting code changes, assessing associated risks, and building a coverage matrix that selects the most efficient test layer for each affected behavior to maximize confidence.

Can I use this approach to plan testing strategies for both backend and frontend changes?▼

Yes, this approach supports planning testing strategies for both backend and frontend changes by evaluating diffs and proposing appropriate test scopes and layered strategies across unit, component, integration, and E2E tests.

How does a coverage matrix help select the right test layer for new features?▼

A coverage matrix maps each affected behavior to the smallest reliable test layer, ensuring maximum confidence. It guides test planning by selecting unit, component, integration, API/contract, or E2E tests based on the specific risk profile.

How do I identify confidence blockers when planning an automated testing strategy?▼

To identify confidence blockers during automated testing strategy planning, analyze the branch diff, map the exhaustive risk-based coverage, and report any gaps or limitations where the selected test layer cannot fully validate the behavior.

When do I need a layered test approach instead of relying solely on unit tests?▼

You need a layered test approach when a feature touches multiple layers and unit tests are insufficient. Analyzing the diff and assessing risks helps determine if integration, API/contract, or E2E tests are required for maximum confidence.

Related Skills

Explore More Software Engineering Skills→
FutureAtomsFutureAtoms
1

git-github-diff-analysis

Analyze Git diffs and assess code change risks and impact.

Community
Advanced
yalishevantyalishevant
14

test-suite-builder

Design layered Kotlin and Spring tests with structured output contracts.

Community
Advanced
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced
GainInsightDevGainInsightDev

af-test-coverage

Analyze Jest coverage reports to identify untested code paths.

Official
Intermediate