bmad-review-verification-gap

Analyze code changes to detect regression, missing-adoption, and broken-verification gaps.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/tiween/tiween --skill bmad-review-verification-gap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-verification-gap
Source: https://github.com/tiween/tiween/tree/main/.agents/skills/bmad-review-verification-gap
Command: npx skills add https://github.com/tiween/tiween --skill bmad-review-verification-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the identification of verification gaps in code changes, helping to ensure that changes do not introduce regressions or issues that are not caught by existing tests.

Core Features & Use Cases

  • Verification Gap Analysis: Identifies potential issues in code changes that could lead to missed regressions.
  • Regression Gap Detection: Finds instances where the changed code regresses but tests do not fail.
  • Missing-Adoption Gap Detection: Identifies places that should adopt new behavior but don't, with no tests flagging the omission.
  • Broken-Verification Gap Detection: Discovers tests that appear to cover changes but are skipped, flaky, or too weak.
  • Use Case: Before merging a code change, use this Skill to ensure it's thoroughly verified to avoid potential issues in production.

Quick Start

Analyze the verification gap in the code change with the command: bmad-review-verification-gap

Frequently Asked Questions about bmad-review-verification-gap

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

FAQPage Schema
What is a verification gap in code changes?

A verification gap occurs when code changes introduce regressions or missing adoptions that existing tests fail to catch. It includes scenarios where tests are skipped, flaky, or too weak to validate the new behavior.

How do I automate regression gap detection before merging code?

You can automate regression gap detection by analyzing code changes within your repository to find instances where changed code regresses but tests do not fail. Run the analysis command before merging to ensure thorough verification.

How does broken-verification gap detection work for skipped or flaky tests?

Broken-verification gap detection works by discovering tests that appear to cover code changes but are actually skipped, flaky, or too weak. It reports these gaps to prevent unverified changes from reaching production.

Can I use code review verification for missing-adoption gap analysis?

Yes, code review verification can identify missing-adoption gaps by finding places in the code that should adopt new behavior but do not, ensuring that tests flag the omission before the code is merged.

When do I need to run a verification gap analysis on my repository?

You need to run a verification gap analysis before merging a code change to ensure it is thoroughly verified. This prevents regressions, missing adoptions, and broken verifications from introducing issues into production.

What is the best way to find tests that are too weak to cover code changes?

The best way to find weak tests is to perform broken-verification gap detection, which discovers tests that appear to cover changes but are skipped, flaky, or lack the assertions needed to fail on regressions.