test-gaps-find

Identify missing, weak, or brittle test coverage by analyzing public contracts and test harnesses.

2|Updated May 18, 2022
One-click install
npx skills add https://github.com/alexfalkowski/bin --skill test-gaps-find
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-gaps-find
Source: https://github.com/alexfalkowski/bin/tree/main/skills/test-gaps-find
Command: npx skills add https://github.com/alexfalkowski/bin --skill test-gaps-find

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of identifying missing, weak, or brittle test coverage in a codebase without manually editing tests, ensuring that repository-owned behaviors are protected by the most appropriate test layers.

Core Features & Use Cases

  • Coverage Triaging: Systematically identifies gaps in test coverage, including flaky, wrong-layer, or brittle tests.
  • Evidence-Based Discovery: Uses existing code, schemas, and runtime evidence to validate gaps rather than relying on stale documentation.
  • Use Case: When preparing for a major refactor, use this skill to audit a specific package to ensure that all public-facing contracts are covered by robust tests, preventing regressions in critical workflows.

Quick Start

Trigger the test-gaps-find skill by asking to find test gaps in the specified package or folder.

Frequently Asked Questions about test-gaps-find

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

FAQPage Schema
How do I find missing test coverage in my codebase before a refactor?▼

Identify missing test coverage by analyzing public contracts and existing test harnesses to systematically triage gaps, ensuring repository-owned behaviors are protected by appropriate test layers before refactoring.

What is test coverage triaging and how does it find weak or brittle tests?▼

Test coverage triaging systematically identifies gaps in test coverage, including flaky, wrong-layer, or brittle tests, using existing code, schemas, and runtime evidence to validate gaps rather than relying on stale documentation.

Can I audit test quality for a specific package without manually editing tests?▼

Yes, you can audit test quality for a specific package without manually editing tests by analyzing public-facing contracts and existing test harnesses to ensure robust coverage and prevent regressions in critical workflows.

What's the best way to ensure public contracts are covered by robust tests?▼

The best way to ensure public contracts are covered is by applying evidence-based discovery to validate gaps using existing code and runtime evidence, ensuring findings are actionable and repository-owned through defined ledger formats.

Why does my test coverage audit require defined ledger formats and delegation gates?▼

Test coverage audits require defined ledger formats and delegation gates to ensure that discovered findings are actionable and repository-owned, maintaining alignment between test layers and architectural boundaries.