forge-releaselisted

Merge approved issue code to production branch and trigger deployment. Use this skill when an issue has been approved at staging and needs to be released — squash-merges the ISS-* feature branch to the production branch, triggers Coolify deploy, and closes the issue. Triggers on: /forge-release, releasing an issue, merging to production, deploying to production. Also use when the pipeline needs to move an issue from released to closed.
SidCorp-co/forge · ★ 4 · AI & Automation · score 73

Install: claude install-skill SidCorp-co/forge

# Forge Release The final step in the issue pipeline: `released → closed`. Squash-merges the ISS-* feature branch to the production branch and triggers deployment. This is a lightweight skill — no codebase exploration, no review. Just merge, deploy, clean up. The ISS-* branch is the single source of truth for the issue's changes. It has been kept alive through the entire pipeline (coding, fixes, reviews). baseBranch (staging) may have commits from other issues mixed in — we never merge baseBranch to production. We merge ISS-* directly. ## Usage ``` /forge-release <documentId> ``` ## Tools - **forge_issues** — get issue data, update status - **forge_comments** — post release comment - **forge_config** — get baseBranch, productionBranch, Coolify config - **forge_coolify_deploy** — trigger production deploy (if configured) - **Bash** — git merge, push, branch cleanup ## Workflow ### Step 0: Local-only mode guard Call `forge_config → get` and `forge_coolify_deploy → list`. If `previewDeploy` is null/missing AND Coolify list is empty → project is in **local-only mode**. In local-only mode, `forge-release` is not applicable — there is no production branch auto-promotion. The pipeline ends at `developed` (human review) and moves to `closed` manually. Post a comment and exit without changing status: ``` forge_comments → create → { data: { body: "**Release skipped** — project is in local-only mode (no Coolify, no preview URL). In this mode the pipeline ends at `develo