happier-release-validation

Run local-first Happier release validation cycles with parallel evidence capture.

1.4k|122|Updated Dec 16, 2025

Search Tags:#session continuity #release validation #evidence capture #upgrade safety #local-first testing #daemon ownership #cross-platform QA

Ready to run

npx skills add https://github.com/happier-dev/happier --skill happier-release-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: happier-release-validation
Source: https://github.com/happier-dev/happier/tree/main/skills/happier-release-validation
Command: npx skills add https://github.com/happier-dev/happier --skill happier-release-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It prevents breaking Happier preview upgrades by validating a candidate release end-to-end on the exact upgrade surfaces users rely on.

Core Features & Use Cases

Local-first release candidate validation: Builds and tests using local candidate artifacts to avoid false confidence from deployed preview scripts.
Cross-platform continuity & upgrade QA: Verifies upgrades and session continuity across CLI, daemon/service, server/relay, and web/mobile flows.
Evidence-driven orchestration with guardrails: Creates a validation worktree, runs parallel automated checks and OS/manual QA lanes, captures evidence, and records findings without ever promoting or releasing.

Quick Start

Use happier-release-validation to validate the candidate version 0.2.6 by running it against your repo, then complete all lanes and evidence capture before any preview promotion.

Frequently Asked Questions about happier-release-validation

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

FAQPage Schema

How do I validate a release candidate for upgrade safety across Linux, macOS, and Windows?▼

You can validate release candidates by running a local-first validation cycle that builds candidate artifacts and tests upgrade safety, daemon ownership, and session continuity across Linux, macOS, and Windows.

What is local-first release validation and why avoid deployed preview scripts?▼

Local-first release validation builds and tests candidate artifacts locally to avoid false confidence from deployed preview scripts, ensuring upgrade surfaces are verified against the exact candidate version before promotion.

Can I run cross-platform QA checks for daemon authentication and session continuity without triggering production side effects?▼

Yes, cross-platform QA checks for daemon authentication and session continuity capture evidence and record findings through parallel lane execution without ever triggering promotion, publish, store submission, or production side effects.

How do I set up a dedicated validation worktree for parallel release testing lanes?▼

Setting up a dedicated validation worktree for release testing involves creating an ignored tracking workspace that orchestrates parallel automated checks and manual QA lanes with reviewer gates for evidence capture.

Does release validation cover native mobile flows and provider launches for preview upgrades?▼

Release validation covers native mobile validate-only flows and provider launches, verifying end-to-end upgrade surfaces including CLI, daemon, server relay, and web UI interactions across supported operating systems.