testing-review

Rerun coverage, identify test gaps, and generate a prioritized roadmap artifact.

16.5k|995|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill testing-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-review
Source: https://github.com/udecode/plate/tree/main/.agents/skills/testing-review
Command: npx skills add https://github.com/udecode/plate --skill testing-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and audit the repository's test suite, rerun coverage, identify test debt, and prepare a proactive testing batch before large changes.

Core Features & Use Cases

  • Audit current test coverage and identify gaps across packages.
  • Score remaining test debt and generate a recommended next batch.
  • Produce a changelog or roadmap artifact with deferrals and statuses for future passes.

Quick Start

Run this skill periodically to audit test coverage and publish the next testing batch.

Frequently Asked Questions about testing-review

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

FAQPage Schema
How do I audit test coverage and identify gaps across repository packages?

Test coverage auditing reruns fresh coverage scans across packages to identify untested code paths, quantify test debt, and surface prioritized gaps ready for the next batching of tests.

What is test debt and how do I score remaining gaps in my test suite?

Test debt represents untested or under-tested code areas. Scoring involves rerunning coverage, scanning results for gaps, and evaluating remaining debt to generate a prioritized plan for future test batches.

How do I create a testing roadmap before large architecture changes?

A testing roadmap maps current coverage gaps, proposes a prioritized next testing batch, and produces an artifact with next steps, deferrals, and statuses to validate architecture changes proactively.

When should I run a test coverage audit for pre-release validation?

Run a test coverage audit during routine quality checks, before large changes, or for pre-release validation to identify untested code paths, map test debt, and prepare a proactive testing batch.

What's the best way to prioritize which tests to write next in my repository?

Prioritizing tests requires rerunning fresh coverage, scoring test debt across packages, and generating a recommended next batch that targets the most critical coverage gaps first for efficient regression testing.