verify

Verifies change completeness by comparing artifacts against implemented code via parallel subagents.

7|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/kirkchen/beat --skill verify-kirkchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/kirkchen/beat/tree/main/skills/verify
Command: npx skills add https://github.com/kirkchen/beat --skill verify-kirkchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify implementation against change artifacts using four dimensions. Uses independent subagents to eliminate context bias.

Core Features & Use Cases

  • Dispatch independent verifiers in parallel to provide objective verification reports.
  • Validate changes against artifacts (design, proposal, tasks) and code under review.
  • Supports multi-dimension verification including behavior, code quality, and test coverage.

Quick Start

Initiate verification by dispatching independent subagents in parallel and review their combined report.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify code changes against design artifacts before deployment?

Independent verification eliminates context bias by dispatching parallel subagents to validate code and artifacts separately, providing an objective, multi-dimension report covering behavior, code quality, and test coverage without prior context.

How to validate task completeness and code quality during a code review?

Parallel verification subagents independently evaluate code behavior, artifact alignment, and test coverage simultaneously, combining their isolated findings into a comprehensive report that confirms whether a change is fully complete and ready.

What is independent verification for change readiness in software engineering?

Independent verification for change readiness is the process of validating implementation completeness by comparing code against design artifacts using parallel subagents, ensuring objective assessment without context bias from the original author.

Does parallel subagent verification work for evaluating test coverage and behavior?

Yes, parallel subagent verification works by independently evaluating test coverage and behavior alongside artifact alignment, running available tests during execution, and combining all dimensions into a single validation report.

What are the limitations of using independent subagents for artifact validation?

A limitation of using independent subagents for artifact validation is that test execution depends on test availability; if no tests are present, the verification report will lack test coverage validation for the implemented code.