Run any Skill in Manus with one click

happier-release-validation-review

Stars1,383

Forks113

UpdatedMay 7, 2026 at 20:06

Review a completed Happier release-validation worktree before any preview promotion. Audits validation fixes, diffs, evidence, lane completion, unresolved risks, and dry-run output. Read-only by default and never releases.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

happier-dev

happier-dev/happier

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	happier-release-validation-review
description	Review a completed Happier release-validation worktree before any preview promotion. Audits validation fixes, diffs, evidence, lane completion, unresolved risks, and dry-run output. Read-only by default and never releases.
metadata	{"openclaw":{"homepage":"https://github.com/happier-dev/happier"}}

Happier Release Validation Review

Use this skill after happier-release-validation finishes and before any release or preview promotion.

Mission

Act as a skeptical release-candidate reviewer. Verify that the validation branch changes are correct, necessary, root-cause-oriented, well-tested, and supported by evidence. Do not promote or release.

Inputs

Validation worktree path
Live workspace under .project/reviews/<date>-v<version>-release-validation/
TRACKING.md, PLAN.md, LEDGER.md, lane docs, evidence directory
git diff for the validation branch
final custom checks result
local release dry-run output

Process

Re-read AGENTS.md.
Read references/review-rubric.md.
In the validation worktree, read TRACKING.md, PLAN.md, and LEDGER.md.
Verify every completed lane has evidence for its claim.
Review every code change made during validation with normal code-review severity.
Confirm tests follow TDD expectations where behavior changed.
Confirm no workaround fixes, hidden skips, destructive cleanup, or release side effects happened.
Review TRACKING.md#Process Feedback and classify each item as back-port now, back-port later, or ignore.
Produce a concise sign-off packet.

Verdicts

APPROVE_FOR_PREVIEW_PROMOTION: evidence and diffs support promotion.
NEEDS_FIXES: specific issues must be fixed before promotion.
NEEDS_MORE_EVIDENCE: claims may be true but evidence is insufficient.
BLOCKED: cannot review because required inputs are missing.

This skill is read-only by default. If fixes are required, ask before editing or direct the user back to happier-release-validation for another fix/validation loop.

More from this repository

same repository

happier-release-notes

happier-dev/happier

Author, update, validate, and publish-ready Happier release-note story decks. Use when creating curated release notes, analyzing commits/diffs/tags to discover user-facing changes, brainstorming detailed and short release notes, adding story-deck cards, adding release-note images/videos/posters, validating translation keys and asset references, preparing happier-assets upload inputs, or updating onboarding showcase story content.

2026-05-111.4k

happier-release-promote

happier-dev/happier

Promote a Happier release only after validation and human review approval. Runs release dry-run first, requires explicit human approval for external side effects, then executes preview or production promotion through the repo release orchestrator.

2026-05-071.4k

happier-release-validation

happier-dev/happier

Run a local-first Happier release validation cycle for a candidate version before preview promotion. Creates a validation worktree and ignored tracking workspace, orchestrates parallel checks, deep manual QA on Lima/macOS/Windows, root-cause fixes, evidence capture, independent reviews, and a final dry-run. This skill never promotes or releases.

2026-05-071.4k

happier-diagnose

happier-dev/happier

Diagnose a problem with a Happier session, the daemon, a provider (Claude/Codex/OpenCode), auth, or connectivity. Pulls the correct logs, finds a true root cause from evidence only, presents findings, and optionally uploads a private diagnostics bundle to Happier developers and/or files a sanitized public GitHub issue (the two are complementary). Use when the user reports a bug, says Happier is broken/stuck/misbehaving, asks to debug/diagnose/triage/troubleshoot Happier, or shares a Happier session ID and asks what went wrong.

2026-04-271.4k

happier-testing

happier-dev/happier

Repo-specific TDD and test-validation workflow for Happier changes, with lane selection, fixture policy, and anti-flake guardrails.

2026-03-221.4k

happier-github-ops

happier-dev/happier

Run GitHub CLI commands as the Happier bot account via `yarn ghops` (forced PAT auth + non-interactive).

2026-02-201.4k

name	happier-release-validation-review
description	Review a completed Happier release-validation worktree before any preview promotion. Audits validation fixes, diffs, evidence, lane completion, unresolved risks, and dry-run output. Read-only by default and never releases.
metadata	{"openclaw":{"homepage":"https://github.com/happier-dev/happier"}}

Happier Release Validation Review

Use this skill after happier-release-validation finishes and before any release or preview promotion.

Mission

Inputs

Validation worktree path
Live workspace under .project/reviews/<date>-v<version>-release-validation/
TRACKING.md, PLAN.md, LEDGER.md, lane docs, evidence directory
git diff for the validation branch
final custom checks result
local release dry-run output

Process

Re-read AGENTS.md.
Read references/review-rubric.md.
In the validation worktree, read TRACKING.md, PLAN.md, and LEDGER.md.
Verify every completed lane has evidence for its claim.
Review every code change made during validation with normal code-review severity.
Confirm tests follow TDD expectations where behavior changed.
Confirm no workaround fixes, hidden skips, destructive cleanup, or release side effects happened.
Review TRACKING.md#Process Feedback and classify each item as back-port now, back-port later, or ignore.
Produce a concise sign-off packet.

Verdicts

APPROVE_FOR_PREVIEW_PROMOTION: evidence and diffs support promotion.
NEEDS_FIXES: specific issues must be fixed before promotion.
NEEDS_MORE_EVIDENCE: claims may be true but evidence is insufficient.
BLOCKED: cannot review because required inputs are missing.

This skill is read-only by default. If fixes are required, ask before editing or direct the user back to happier-release-validation for another fix/validation loop.