OpenParable
Skip to content
← Back to skills

Happier Release Promote

DevOps & Security
happier-release-promote

Happier Release Promote is an Agent Skill for devops & security published in the happier-dev/happier repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/happier-dev/happier/blob/HEAD/skills/happier-release-promote/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/happier-release-promote, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Happier Release Promote

Use this skill only after happier-release-validation-review approves the candidate.

Mission

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.

Required Inputs

  • Human approval from validation review
  • Target lane: preview or production
  • Candidate branch/worktree
  • Bump mode
  • Deploy targets
  • Mobile/desktop action choices, if any

Process

  1. Re-read AGENTS.md.
  2. Read references/promotion-commands.md.
  3. Confirm validation review verdict is APPROVE_FOR_PREVIEW_PROMOTION or equivalent production approval.
  4. Run dry-run command.
  5. Summarize planned side effects.
  6. Ask for explicit approval to run the real command.
  7. Execute only after approval.
  8. Monitor GitHub/release jobs until completion.
  9. Verify the post-publish release-verify.yml result when the release profile triggers it, or explicitly record why it was skipped.
  10. Report published versions/artifacts and any follow-up verification.

Never bypass node scripts/pipeline/run.mjs release for full releases unless the user explicitly requests a manual partial publish.

Target Discipline

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.