ce-test-creator

Generate targeted tests for documented coverage gaps using the ADR-030 workflow.

78|15|Updated May 1, 2023
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-test-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-test-creator
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-test-creator
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-test-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Close documented coverage gaps by generating targeted tests that improve signal-to-noise and reduce padding in test suites.

Core Features & Use Cases

  • Gap-analysis-driven test creation: identifies missing coverage from documented gaps and proposes precise, high-value tests.
  • Option-aware workflow: supports Option A (test-focused), Option B (code-focused), and Option C (full cycle) to coordinate with existing changes.
  • Evidence-backed proposals: outputs target behavior, target module/function, rationale, expected coverage gain, and the chosen option.

Quick Start

Use ce-test-creator to generate a focused test proposal for a known gap and submit it for review.

Frequently Asked Questions about ce-test-creator

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

FAQPage Schema
How do I generate targeted tests to close documented coverage gaps?▼

Generate targeted tests by applying the ADR-030 Test Creator workflow to documented coverage gaps, ensuring proposed tests cover unique lines or behavioral contracts while providing a structured output detailing target behavior and rationale.

What is the ADR-030 test creation workflow for gap analysis?▼

The ADR-030 test creation workflow is a structured process that identifies missing coverage from documented gaps and proposes precise, high-value tests to improve signal-to-noise and reduce padding in test suites.

How do I choose between Option A, B, or C for test creation scope?▼

Choose between Option A (test-focused), Option B (code-focused), and Option C (full cycle) to coordinate test creation with existing changes, tailoring the testing scope to match your specific development context and avoid padding.

Does gap-analysis-driven test creation work for existing test suites?▼

Yes, gap-analysis-driven test creation works for existing test suites by identifying missing coverage from documented gaps and proposing evidence-backed tests that detail target behavior, module, rationale, expected coverage gain, and the selected option.

What's the best way to avoid test padding when closing coverage gaps?▼

Avoid test padding by using gap-analysis to generate targeted tests that cover unique lines or behavioral contracts, ensuring each proposed test provides high-value coverage backed by evidence and a clear rationale.

When should I not use automated test creation for coverage gaps?▼

You should not use automated test creation for coverage gaps if your codebase does not follow the ADR-030 Test Creator workflow, as the structured output and option-aware workflow depend on this specific architectural decision record.