verify

Run Step 4 verification gate checks and generate an APPROVED or REJECTED report.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nullhack/pytest-beehave --skill verify-nullhack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/verify
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill verify-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independent verification and reporting are essential to ensure that a feature meets quality standards and that stakeholders receive a clear, auditable verdict.

Core Features & Use Cases

  • Structured gate checks: lint, static-checks, and tests are run as part of Step 4 to validate readiness.
  • Self-Declaration Audit: a formal checklist that documents evidence and yields a final APPROVED or REJECTED decision.
  • Formal reporting: generates a written verification report suitable for review and handoff to product owners.

Quick Start

Run the Step 4 verification workflow to generate the final decision report.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate code review gate checks for lint, static checks, and tests?

Code review gate checks validate feature readiness by running lint, static checks, and tests as structured validation steps. This workflow automates those gate checks during Step 4 to produce an evidence-backed APPROVED or REJECTED verdict for stakeholders.

What is a self-declaration audit in feature verification workflows?

A self-declaration audit in feature verification is a formal checklist that documents evidence to yield a final APPROVED or REJECTED decision. It ensures thorough checks are completed and generates a formal verification report for handoff to product owners.

How do I generate a formal verification report with an APPROVED or REJECTED verdict?

To generate a formal verification report with an APPROVED or REJECTED verdict, run the Step 4 verification workflow. This process automates gate checks, completes the self-declaration audit, and outputs a written decision document for review.

Does independent verification reporting work for audit trails during code review?

Yes, independent verification reporting works for audit trails by generating a written Step 4 report with an APPROVED or REJECTED verdict. It ensures evidence-backed decision making and satisfies requirements for thorough checks during code review.

When do I need an end-to-end verification workflow with static checks and linting?

You need an end-to-end verification workflow with static checks and linting when a feature requires rigorous gate checks, audit trails, and evidence-backed decision making. It is essential for producing formal decision documents during code review handoffs.