hyper-verify

Run tests, triage code review, and validate acceptance criteria into checks.md.

2|1|Updated Apr 20, 2026

Search Tags:#qa #backlog #verify #code-review #tests #hyper

Ready to run

npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hyper-verify
Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-verify
Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the verify phase to ensure implemented changes meet tests, security reviews, and acceptance criteria before release.

Core Features & Use Cases

Runs tests to confirm green builds.
Performs triage of code changes via hyper-code-review and QA against acceptance criteria.
Generates a single checks.md with a pass/needs-changes/blocked verdict and supports opt-out gating and backlog updates.

Quick Start

Run a verify dispatch for the current task and review the resulting checks.md verdict.

Frequently Asked Questions about hyper-verify

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

FAQPage Schema

How do I automate QA verification and code review for backlog tasks?▼

Automate QA verification by running tests, performing triage code review, and validating acceptance criteria in a single pass. This orchestrates tests, review, and QA to produce a checks.md artifact with a pass, needs-changes, or blocked verdict for backlog tasks.

What is a checks.md artifact in end-to-end task verification?▼

A checks.md artifact is a structured output file generated during end-to-end task verification. It contains a final verdict of pass, needs-changes, or blocked, summarizing the results of automated tests, triage code review, and acceptance criteria validation.

When should I run automated tests and code review together?▼

Run automated tests and code review together when a task enters the verify phase after implementation. Orchestrating tests, review, and QA in a single pass ensures implemented changes meet security reviews and acceptance criteria before release.

How do I handle opt-out gates and backlog updates during the verify phase?▼

Handle opt-out gates and backlog updates during the verify phase by running an automated verification dispatch. The process evaluates gating conditions and interacts with backlog management as needed to output the final checks.md verdict.

Does hyper-verify work without external dependencies?▼

Yes, the hyper-verify skill operates with no external dependencies. It orchestrates tests, code review, and acceptance criteria validation internally to generate the final checks.md verdict for tasks in the verify phase.

What is the best way to validate user-facing acceptance criteria before release?▼

The best way to validate user-facing acceptance criteria is to run an automated verification pass that checks builds, performs triage code review, and tests criteria compliance. It outputs a structured checks.md file with a clear pass or blocked verdict.