test-suite-comprehension

Map source modules to tests and produce a ranked coverage gap report.

12|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill test-suite-comprehension
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-suite-comprehension
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/test-suite-comprehension
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill test-suite-comprehension

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map a project's test suite against its source files and surface where verification gaps live. Returns a coverage summary, a gap report ranked by risk, and the specific test files that are highest-leverage places to add coverage.

Core Features & Use Cases

  • Coverage mapping: Aligns source modules with tests to show which parts are tested and which are not.
  • Gap ranking: Produces a risk-scored gap report highlighting modules with the largest blast radius and most critical failure modes.
  • Recommendations & hygiene: Suggests 3-10 high-leverage test additions and surfaces suite hygiene observations.
  • Use Case: Before opening a PR that adds substantial logic, verify the verification surface matches the implementation surface.

Quick Start

Run the Activation preflight from METHODOLOGY.md before proceeding.

Frequently Asked Questions about test-suite-comprehension

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

FAQPage Schema
How do I find test coverage gaps in a multi-repo project?▼

To find test coverage gaps, analyze the codebase's test suite against source modules and cross-reference manifests, tests, and coverage data. This surfaces untested modules and produces a ranked gap report without altering source code or CI configuration.

Can I use test suite analysis to recommend specific test additions?▼

Yes, test suite analysis recommends 3-10 high-leverage test additions based on the ranked gap report. It identifies the specific test files that are highest-leverage places to add coverage and writes the results to a markdown planning file.

Does test gap analysis work with multi-repo projects without changing CI configuration?▼

Yes, test gap analysis works with multi-repo projects by cross-referencing manifests, tests, and coverage data. It operates strictly in read-only mode, writing results to a markdown file without altering source code or CI configuration.

What's the best way to rank test coverage gaps by risk?▼

The best way to rank test coverage gaps by risk is to score them based on blast radius and critical failure modes. This produces a ranked gap report that prioritizes modules needing coverage and highlights suite hygiene observations.

When should I run a test suite comprehension analysis?▼

You should run a test suite comprehension analysis before opening a PR that adds substantial logic. This verifies that the verification surface matches the implementation surface and ensures new code is adequately covered by tests.