nexus-a1/merge-release
skills/merge-release/SKILL.md
Merge an approved release PR into its target branch. Validates approval/checks/conflicts via gh, then merges. Step 3 of the release workflow.
testing
Updated May 2, 2026
$ install --global
skillsauthnpx skillsauth add nexus-a1/claude-skills merge-releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 2, 2026, 4:52 AM156.5s1 file scanned
SKILL.md
- name:
- merge-release
- category:
- release-management
- model:
- claude-haiku-4-5
- userInvocable:
- true
- description:
- Merge an approved release PR into its target branch. Validates approval/checks/conflicts via gh, then merges. Step 3 of the release workflow.
- argument-hint:
- [release-branch | version]
- allowed-tools:
- Bash(pwd:*), Bash(git rev-parse:*), Bash(git branch:*), Bash(git fetch:*), Bash(bash:*), AskUserQuestion
Merge Release PR Command
Workflow:
/create-release-branch→/create-release→/merge-release→/release
Context
Working directory: !pwd
Current branch: !git branch --show-current 2>/dev/null || echo "(not in a git repository)"
Available release branches: !git branch -a --list 'release/*' 'origin/release/*' 2>/dev/null || echo "(no release branches)"
Arguments provided: $ARGUMENTS
Release terminology — see ${CLAUDE_PLUGIN_ROOT}/shared/release-concepts.md.
Your Task
Thin dispatcher over ${CLAUDE_PLUGIN_ROOT}/shared/release/pr-merge.sh. Do not re-derive validation logic in prose — call the script and surface its structured output. Run all steps in a single message; no per-step reasoning rounds.
Step 0 — Pre-flight: verify git repo
git rev-parse --is-inside-work-tree 2>/dev/null
If non-zero, stop with the standard "not in a git repository" message instructing the user to cd into a service repo.
Step 1 — Parse arguments
bash "${CLAUDE_PLUGIN_ROOT}/shared/release/parse-args.sh" \
--skill=pr-merge --json -- $ARGUMENTS
Outcomes:
- Exit 0 —
release_branchpopulated; proceed. - Exit 10 —
missingcontainsrelease_branch. Go to Step 2 (interactive selection). - Exit 20 — show errors and stop.
Step 2 — Interactive selection (no arg supplied)
List open release-labeled PRs:
bash "${CLAUDE_PLUGIN_ROOT}/shared/release/pr-merge.sh" --list --json
If the array is empty, stop with: "No open release PRs found. Run /create-release first."
Otherwise use AskUserQuestion to present each PR as an option (label: #<n> <headRefName> → <baseRefName>, description: title). The user picks one; remember its headRefName as release_branch.
Step 3 — Plan: show PR state and gates
bash "${CLAUDE_PLUGIN_ROOT}/shared/release/pr-merge.sh" \
--release-branch=<release_branch> --plan --json
The output JSON has:
pr— number, title, url, state, mergeable, reviewDecision (rawstatusCheckRollupis stripped — already aggregated below)gates—approved,no_conflicts,checks_passing,checks_running,readyfailing_checks[]— slim{name, conclusion}per failed check, used to name what failedrunning_checks_count— count of checks still pending/in-progress (no per-check detail)blocking_issues— human-readable list of why it's not ready (empty when ready)
Render a short summary to the user (one section per gate, ✓ / ✗).
If pr.state == "MERGED", congratulate the user and stop — there is nothing to do.
If pr.state == "CLOSED", surface the URL and stop.
Step 4 — Decide whether to merge
If gates.ready == true, use AskUserQuestion to confirm: Merge PR #N now? [y/n]. Also ask whether to delete the release branch after merge (pass --delete-branch on apply if yes).
If gates.ready == false, surface blocking_issues and AskUserQuestion to ask the user how to proceed. Valid options depend on which gate failed:
| Failed gate | Allowed user choices |
|--------------------------|---------------------------------------------------------------------------------|
| no_conflicts == false | Abort only — conflicts must be resolved on the branch first. |
| checks_running | Abort, or wait and re-run /merge-release. |
| checks_passing == false| Abort, view details (gh pr checks <n>), or merge anyway (override). |
| approved == false | Abort, or merge anyway (override; review-required is a soft gate). |
When the user opts to override, pass the relevant flag(s) to apply: --allow-unapproved, --allow-failing-checks. Conflicts cannot be overridden — direct the user to resolve them and re-run.
Step 5 — Apply
bash "${CLAUDE_PLUGIN_ROOT}/shared/release/pr-merge.sh" \
--release-branch=<release_branch> --apply --json \
[--allow-unapproved] [--allow-failing-checks] [--delete-branch]
The merge happens server-side (GitHub API) — no git push is issued, so the audit-gate hook does not apply.
If apply exits non-zero, surface stderr verbatim and stop.
Step 6 — Report
On success:
✓ Release PR Merged
PR: #<n> <title>
branch: <head> → <base>
Next:
/release # tag + GitHub release
Important Notes
- Single message execution — run all steps in one assistant turn; use parallel tool calls where independent.
- No re-derived gh commands in prose — every gh call goes through
pr-merge.sh(orgh pr listin Step 2 when listing). - No audit recording needed — the merge and optional branch deletion are server-side via the GitHub API.
Related Skills
nexus-a1/add-product-knowledge
development
VerifiedTrustedCommunity
Add a new entry to the product knowledge base. Wizard-guided — prompts for category, title, and content, then writes a structured markdown file and rebuilds the manifest.
SKILL.mdUpdated Apr 24, 2026
nexus-a1/work-status
data-ai
VerifiedTrustedCommunity
Show all active work sessions across brainstorms, requirements, proposals, and epics. Supports --update to advance lifecycle on one session and --sync to sweep them all.
SKILL.mdUpdated Apr 23, 2026
nexus-a1/update-documentation
documentation
VerifiedTrustedCommunity
Review and update project documentation using an agent team. Inventories docs, identifies gaps and drift, updates technical and API docs in parallel.
SKILL.mdUpdated Apr 17, 2026
nexus-a1/update-context
tools
VerifiedTrustedCommunity
Annotate an active work session with a note, scope change, or new finding. Auto-detects the active session, synthesizes the salient points of the current conversation, and appends a timestamped entry to state.json after a single target confirmation. Use mid-session when you learn something that should be preserved.
SKILL.mdUpdated Apr 17, 2026