stv-verify

Compare issue acceptance criteria against GitHub PR changes to report gaps.

36|3|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/2lab-ai/oh-my-claude --skill stv-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stv-verify
Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/verify
Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill stv-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-checks ensure the acceptance criteria defined in an issue are verifiably satisfied by the corresponding PR, preventing drift and merge blockers.

Core Features & Use Cases

  • Cross-check issue specs with PR changes to validate completeness, correctness, and coherence.
  • Perform a gap analysis to surface deviations such as assumption injection, scope creep, direction drift, missing core, and over-engineering.
  • Generate a verdict and a dimensional assessment to guide PR approvals and release readiness.

Quick Start

Provide the issue URL and PR URL to start the verification.

Frequently Asked Questions about stv-verify

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

FAQPage Schema
How do I verify a pull request against Jira issue acceptance criteria?

Verify PR changes against Jira issue acceptance criteria by providing the issue URL and PR URL, which inspects changed files and specs to report alignment gaps and generate a release readiness verdict.

What is PR gap analysis and how does it detect scope creep?

PR gap analysis compares code changes against issue specs to detect deviations such as scope creep, assumption injection, direction drift, and over-engineering, ensuring the implementation matches the defined requirements.

How do I check if a GitHub PR meets the defined issue spec?

Check if a GitHub PR meets the defined issue spec by cross-referencing the descriptive acceptance criteria with the changed files to evaluate completeness, correctness, and coherence, surfacing any missing core functionality.

Can I use this to automate release readiness checks for issue-based tasks?

Yes, you can automate release readiness checks for issue-based tasks by generating a verdict and dimensional assessment that guides PR approvals and prevents merge blockers caused by spec drift.

What do I need to provide to start a conformance check on a pull request?

To start a conformance check on a pull request, you need to provide the issue URL and the PR URL, along with any optional trace documents, to evaluate alignment with the defined spec.

Why does PR review fail to catch direction drift in issue-based tasks?

PR review fails to catch direction drift when it lacks automated cross-checks against issue intent, making it necessary to compare acceptance criteria with changed files to ensure code meets the defined spec.