he-verify-release

Verify release readiness by checking test evidence, invariants, and rollback feasibility.

4|1|Updated Feb 14, 2026

Search Tags:#testing #deployment #rollback #verification #release #evidence

Ready to run

npx skills add https://github.com/mattjefferson/harness-engineering --skill he-verify-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: he-verify-release
Source: https://github.com/mattjefferson/harness-engineering/tree/main/skills/he-verify-release
Command: npx skills add https://github.com/mattjefferson/harness-engineering --skill he-verify-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that software releases are thoroughly checked for readiness, including tests, invariants, and rollback plans, before deployment, preventing potential issues and ensuring a smooth release process.

Core Features & Use Cases

Gate Verification: Independently verifies critical gates such as test pass rates, architectural invariants, and security review status.
Evidence Collection: Gathers and records evidence for user-visible changes, including agentic E2E artifacts.
Decision Recording: Formally records a GO/NO-GO decision in the active plan, with clear rationale and rollback procedures.
Use Case: After a feature has been reviewed and coded, this skill will run all automated tests, check architectural rules, confirm the security review passed, and document the rollback steps, ultimately deciding if the release is ready to proceed.

Quick Start

Use the he-verify-release skill to validate the readiness of the current release candidate.

Frequently Asked Questions about he-verify-release

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

FAQPage Schema

How do I verify release readiness before deployment?▼

Release readiness verification checks test evidence, invariant conditions, and rollback feasibility to produce a documented go/no-go decision. This process ensures all review gates pass and evidence for user-visible changes is captured before deployment proceeds.

What is a go/no-go decision in software deployment?▼

A go/no-go decision is a formal release gate determination recorded in the active plan based on test pass rates, architectural invariants, and security review status. It escalates uncertainty by requiring explicit rollback procedures before approving deployment.

How do I check if rollback procedures are feasible before a release?▼

Rollback feasibility is checked by verifying that rollback procedures are explicit, documented, and actionable within the active plan. This ensures that if deployment issues arise, the rollback steps have been validated prior to execution.

How do I collect evidence for user-visible changes during release verification?▼

Evidence collection for user-visible changes gathers and records artifacts, including agentic end-to-end test results. This documentation proves that critical gates passed and validates the release candidate's behavior before the final deployment decision.

What happens if architectural invariants fail during release verification?▼

When architectural invariants fail verification, the release process escalates the uncertainty and records a no-go decision. This prevents deployment by ensuring all critical architectural rules and security reviews pass before proceeding.

Can I automate release verification for test pass rates and security reviews?▼

Release verification independently automates checks for test pass rates, architectural invariants, and security review status. It aggregates these results to formally record a deployment decision, ensuring no gate is manually skipped.