x-test-matrix

Generate or refresh a repository-wide TEST-MATRIX document from test layers and coverage output.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/pure-golang/level85 --skill x-test-matrix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-test-matrix
Source: https://github.com/pure-golang/level85/tree/main/.agents/skills/x-test-matrix
Command: npx skills add https://github.com/pure-golang/level85 --skill x-test-matrix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of scattered or outdated documentation about what tests exist, which layers they cover, and whether coverage is actually enforced.

Core Features & Use Cases

  • Creates or updates TEST-MATRIX: Generates or refreshes docs/TEST-MATRIX.md using the repo’s required template so the structure stays consistent.
  • Inventory by layers: Maps unit tests, API BDD runner coverage, browser BDD runner coverage, and smoke checks into a clear layer-by-layer view.
  • Adds coverage visibility: Captures package-level coverage indicators and includes a code coverage section based on running the project’s coverage task.

Quick Start

Use the x-test-matrix skill to update docs/TEST-MATRIX.md after you change or move tests between layers, ensuring the output follows assets/TEST-MATRIX.md.tmpl without restructuring.

Frequently Asked Questions about x-test-matrix

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

FAQPage Schema
How do I generate a test matrix document for my repository?

Generate a repository-wide TEST-MATRIX document by inventorying unit tests, BDD runners, smoke checks, and code coverage into the required template format. The output maps test layers and feature coverage into a clear, consistent view for review and release workflows.

What is a test matrix used for in release readiness workflows?

A test matrix is used during release readiness to document what tests exist, which layers they cover, and whether coverage is enforced. It inventories unit, BDD, and smoke layers alongside code coverage summaries to provide a single source of truth for handoffs.

How do I document unit tests and BDD runner coverage in one place?

Document unit tests and BDD runner coverage by mapping API and browser BDD runners, smoke checks, and unit tests into a layer-by-layer view within a single TEST-MATRIX file. This captures test case lists and package-level coverage indicators using the project's coverage task output.

Does the test matrix template support repositories without browser BDD tests?

The test matrix template supports repositories without browser BDD tests by only including layers that actually exist. It inventories unit, API BDD, browser BDD, and smoke test layers, but omits any layer not present in the repository without unapproved restructuring.

When should I update my repository's test documentation after test landscape changes?

Update your repository's test documentation when you change or move tests between layers, ensuring the TEST-MATRIX reflects the current test landscape. This preserves stable test IDs and maintains accurate coverage visibility for review and handoff workflows.