// 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.
| name | happier-release-promote |
| description | 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. |
| metadata | {"openclaw":{"homepage":"https://github.com/happier-dev/happier"}} |
Use this skill only after happier-release-validation-review approves the candidate.
Perform the actual release promotion through the canonical repo release orchestrator. This skill has external side effects and must always ask for explicit human approval before the non-dry-run command.
AGENTS.md.references/promotion-commands.md.APPROVE_FOR_PREVIEW_PROMOTION or equivalent production approval.release-verify.yml result when the release profile triggers it, or explicitly record why it was skipped.Never bypass node scripts/pipeline/run.mjs release for full releases unless the user explicitly requests a manual partial publish.
Preview and production have different gates. Use this skill with an explicit target:
preview: promote dev to preview after validation review approval.production: promote preview to main only after preview soak and separate production approval.Deploy webhook calls may require Cloudflare Access service tokens. If required credentials are missing, stop and report the missing secret; do not attempt unauthenticated workarounds.
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.
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.
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).