test-coverage

Identify and document test coverage gaps in AI-generated test suites.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sunbluesome/dotfiles --skill test-coverage-sunbluesome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/sunbluesome/dotfiles/tree/main/.claude/ds/skills/test-coverage
Command: npx skills add https://github.com/sunbluesome/dotfiles --skill test-coverage-sunbluesome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams identify and document gaps in test coverage for AI-generated tests, enabling quick visibility into missing or insufficient tests.

Core Features & Use Cases

  • Organize tests along processing flow diagrams to visualize which tests exist for each processing step.
  • Before implementation: Systematically identify required test cases.
  • After implementation: Verify if existing tests are sufficient.
  • Reference shared prefixes to maintain consistent taxonomy across related skills.

Quick Start

Provide your feature area and issue, then generate a test-coverage report by mapping tests to the processing flow and listing gaps.

Frequently Asked Questions about test-coverage

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

FAQPage Schema
How do I identify test coverage gaps in AI-generated test suites?

To identify test coverage gaps, you can map existing AI-generated tests against processing flow diagrams to visualize missing scenarios and generate a structured matrix documenting the insufficient coverage areas.

What is the best way to design test cases before implementation using BDD?

Designing test cases before implementation involves mapping required behaviors to a processing flow diagram and generating a test matrix, ensuring systematic identification of necessary BDD scenarios.

How do I verify if existing tests are sufficient after implementation?

Verifying test sufficiency after implementation requires mapping current tests to the processing flow and generating a coverage matrix to quickly visualize any missing or insufficient test cases.

Can I enforce consistent taxonomy across related test documentation?

Yes, you can maintain consistent taxonomy across related documentation by referencing shared prefixes, which enforces template requirements for category checklists and structured matrix guidance.

How do I link test matrices to feature files for quality assurance?

Linking test matrices to feature files requires enforcing strict template requirements for link formatting, ensuring your quality assurance documentation maps directly to the underlying test suites.

What limitations exist when documenting test coverage using processing flow diagrams?

Documenting test coverage using processing flow diagrams requires strict adherence to template rules for category checklists and link formatting, meaning deviations can break the structured matrix output.