Menu
Promote develop to main — apply any pending migrations, open the develop→main PR with Closes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pick up a GitHub issue by number and drive it from clarification through implementation, PR, a single automated review pass, and fixing the resulting remarks. Use when the user gives a bare ticket/issue number and asks to implement, pick up, or ship it (e.g. "/implement-ticket 123", "pick up ticket 123", "implement issue
Run a design-review session on an existing page — create the branch, invoke frontend-design, build incrementally with screenshots, then PR into develop. Use when visually overhauling an existing page or section.
Kick off a new feature — stress-test the plan with grill-with-docs, break it into tickets with to-issues, then commit any doc changes to develop. Use when you have a feature idea or rough plan and want to go from concept to a clean set of GitHub issues.
Run the post-merge checklist after a feature PR lands on develop — pull latest, add awaiting-promotion label to the issue, update CLAUDE.md/CONTEXT.md if stale, and commit docs directly to develop. Use when a feature PR has just merged into develop and you want to run the standard follow-up steps.
| name | promote |
| description | Promote develop to main — apply any pending migrations, open the develop→main PR with Closes |
| disable-model-invocation | true |
Drives the full develop → main promotion. Five steps, in order.
Check whether the project has any prerequisites that must be completed before the PR goes live — for example, database migrations, infrastructure changes, or third-party configuration that the code depends on. Apply any that are outstanding before opening the PR.
If the project tracks these in a documentation file, update that file to reflect they've been applied and commit the change directly to develop before continuing.
If there are no prerequisites, skip to step 2.
List open issues labelled awaiting-promotion — these are the ones landing in this promotion:
gh issue list --label "awaiting-promotion" --state open
Note their numbers — you'll need them in the PR body.
gh pr create --base main --head develop --title "Promote develop → main" --body "$(cat <<'EOF'
## What's included
<brief summary of the changes being promoted>
## Closes
Closes #N
Closes #M
EOF
)"
Closes #N line for every issue from step 2.Closes references here (not in feature PRs) is correct — this is the merge that ships to production.Wait for the PR to merge. Verify the deploy is healthy before step 5.
For every issue that was closed by the promotion PR, swap its label:
gh issue edit <N> --remove-label "awaiting-promotion" --add-label "promoted"
Repeat for each closed issue. Do both operations in the same command — removing without adding the promoted label is incomplete.
If the promoted label doesn't exist yet:
gh label create "promoted" --color "0075ca"
Closes #N in feature→develop PRs. Only here, in the promote PR.Closes references get unwieldy, close them manually post-merge rather than skipping them.awaiting-promotion label should be empty. If any remain, they weren't in this promotion — leave them as-is.main and merged directly should be back-merged into develop so the fix isn't lost at the next promotion.