// 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.
| 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"}} |
Use this skill after happier-release-validation finishes and before any release or preview promotion.
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.
.project/reviews/<date>-v<version>-release-validation/TRACKING.md, PLAN.md, LEDGER.md, lane docs, evidence directorygit diff for the validation branchAGENTS.md.references/review-rubric.md.TRACKING.md, PLAN.md, and LEDGER.md.TRACKING.md#Process Feedback and classify each item as back-port now, back-port later, or ignore.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.
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.
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.
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.
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.
Repo-specific TDD and test-validation workflow for Happier changes, with lane selection, fixture policy, and anti-flake guardrails.
Run GitHub CLI commands as the Happier bot account via `yarn ghops` (forced PAT auth + non-interactive).