happier-release-validation-review

Review Happier release-validation worktrees and emit a promotion verdict.

1.4k|122|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/happier-dev/happier --skill happier-release-validation-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: happier-release-validation-review
Source: https://github.com/happier-dev/happier/tree/main/skills/happier-release-validation-review
Command: npx skills add https://github.com/happier-dev/happier --skill happier-release-validation-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents unsafe or under-evidenced releases by forcing a skeptical, evidence-driven review of a Happier release-validation worktree before any preview promotion.

Core Features & Use Cases

  • Evidence-first lane verification: Confirms every completed lane includes evidence that substantiates its claim.
  • Release-candidate code review: Reviews all diffs from the validation branch with appropriate severity and maps changes to recorded failures, risks, or validation needs.
  • Safety and side-effect guardrails: Ensures validation produced no release/promotion/publish side effects and that custom checks and dry-run outputs were completed.
  • Process feedback triage: Reviews TRACKING.md#Process Feedback items and classifies each as back-port now, back-port later, or ignore, producing a concise sign-off packet.

Quick Start

Have the skill run against your completed happier-release-validation worktree to produce findings and a final promotion verdict, including a sign-off packet.

Frequently Asked Questions about happier-release-validation-review

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

FAQPage Schema
How do I validate release evidence before promoting a release candidate?

Release validation audits a completed worktree to verify evidence mapping and lane completeness before promotion. It reviews test evidence, git diffs, and dry-run outputs to ensure every claim is substantiated before a release candidate is approved.

What is a promotion gate and when do I need to check it?

A promotion gate is a preview checkpoint requiring validation lanes, evidence, and dry-run verification before any release side effects occur. You need to check it when deciding whether a release candidate is safe for promotion.

How do I review git diffs and classify process feedback for a release validation?

Review git diffs by mapping changes to recorded failures and validation needs. Classify process feedback items from TRACKING.md as back-port now, back-port later, or ignore to produce a concise sign-off packet with residual risks identified.

Does release validation require reading AGENTS.md and review rubric references?

Yes, release validation requires reading AGENTS.md and review-rubric references to verify plan completeness and evidence mapping. These references provide the standards needed to emit a promotion verdict with residual risks.

How do I ensure validation produced no release or publish side effects?

Safety guardrails within release validation check that no release, promotion, or publish side effects occurred. It confirms that custom checks and dry-run outputs were completed without triggering unintended side effects.