speckit-review-tests

Identify test coverage gaps in pull requests for behavioral resilience.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-review-tests-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-review-tests
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-review-tests
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-review-tests-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers identify gaps in test coverage for pull requests, prioritizing behavioral coverage and resilience to ensure critical functionality is tested.

Core Features & Use Cases

  • Behavioral coverage assessment: evaluates whether changes are tested by scenarios that reflect real user behavior.
  • Critical gap identification: highlights untested paths, edge cases, and error conditions that could lead to regressions.
  • Test resilience evaluation: suggests robust test patterns and regression checks to withstand refactors and integration changes.

Quick Start

Execute a behavior-focused review of the current PR to surface missing tests and recommended coverage improvements.

Frequently Asked Questions about speckit-review-tests

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

FAQPage Schema
How do I identify gaps in behavioral test coverage during a pull request review?

To identify gaps in behavioral test coverage during a PR review, evaluate whether changes are tested by scenarios reflecting real user behavior, focusing on critical code paths, edge cases, and failure modes to prevent regressions.

What is behavioral test coverage and how does it differ from standard code coverage?

Behavioral test coverage assesses whether pull request changes are tested by scenarios reflecting real user behavior, rather than just executed lines, ensuring critical functionality and resilience are validated against actual contracts.

How do I ensure my PR tests are resilient to refactoring and integration changes?

To ensure PR tests are resilient to refactoring, evaluate test resilience by applying robust test patterns and regression checks that verify behavioral contracts and withstand integration changes without breaking.

Can I analyze untested error conditions and edge cases in my spec-kit workflow?

Yes, you can analyze untested error conditions and edge cases in a spec-kit workflow by performing a behavior-focused review to surface missing tests, prioritize actionable gaps, and provide concrete test recommendations.

What is the best way to prioritize missing tests in a pull request?

The best way to prioritize missing tests in a pull request is to evaluate test gaps based on behavioral coverage, highlighting untested paths and error conditions that pose the highest regression risk.