test-gaps-implement

Implement confirmed test coverage gaps using a scoped ledger and TDD phases.

2|Updated May 18, 2022

Search Tags:#testing #tdd #refactoring #coverage #quality-assurance #ledger

Ready to run

npx skills add https://github.com/alexfalkowski/bin --skill test-gaps-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-gaps-implement
Source: https://github.com/alexfalkowski/bin/tree/main/skills/test-gaps-implement
Command: npx skills add https://github.com/alexfalkowski/bin --skill test-gaps-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining high-quality test coverage by providing a structured, evidence-based workflow for identifying and implementing missing test cases in a repository.

Core Features & Use Cases

Evidence-Based Implementation: Ensures that test gaps are only addressed when supported by non-prose evidence and explicit human request.
Standardized Ledger Management: Uses a formal ledger format to track coverage risks, reproduction steps, and validation criteria.
Workflow Integration: Coordinates with existing test harnesses and project standards to ensure that new tests align with the repository's established testing patterns.

Quick Start

Use the test-gaps-implement skill to review and implement the confirmed test gap entry identified in the ledger for the specified scope.

Frequently Asked Questions about test-gaps-implement

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

FAQPage Schema

How do I implement missing test coverage gaps using a structured TDD workflow?▼

To implement test coverage gaps, this skill validates repository-owned behavior through established test layers using a strict TDD cycle of red, green, refactor, and validation phases. Test additions are evidence-based, minimal, and aligned with project-specific testing standards.

What is the best way to track test coverage risks and reproduction steps during refactoring?▼

Tracking test coverage risks is managed through a formal, scoped ledger format that records reproduction steps and validation criteria. This ensures that test gap implementations are evidence-based and explicitly requested by a human before execution.

How do I ensure new tests align with existing test harnesses and project quality assurance standards?▼

To ensure new tests align with existing test harnesses, this skill coordinates with established repository testing patterns and project standards. It guarantees that test additions fit the repository's owned behavior and standardized ledger management.

Can I add tests automatically without non-prose evidence in my repository?▼

You cannot add tests without evidence, as this skill enforces evidence-based implementation. Test gaps are only addressed when supported by non-prose evidence and an explicit human request, ensuring minimal and verified test additions.

Why does my test gap implementation require a strict red, green, refactor, and validation cycle?▼

The strict red, green, refactor, and validation cycle is required to maintain high-quality test coverage. This TDD-inspired implementation cycle ensures that all test additions accurately validate repository-owned behavior before integration.

What limitations exist when using a scoped ledger to implement test gaps?▼

The limitation of using a scoped ledger is that test gap implementation is restricted to confirmed ledger entries for a specified scope. It requires strict adherence to the ledger's evidence and validation criteria before adding any tests.