Menu
Safe PR merge with check verification, post-merge cleanup, and migration reminder.
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
Apply Jobs-to-be-Done (Christensen / Competing Against Luck flavor) to a feature idea, document, or problem statement. Produces a JTBD canvas with the job, the struggling moment, desired progress, current alternatives, and hire/fire criteria. Flags where the stated feature is a solution masquerading as a job, and where evidence is thin. Use when shaping a feature, challenging a brief, or interpreting customer research.
Apply MoSCoW prioritization (Must / Should / Could / Won't) to a list of candidate solutions, defending each placement against explicit criteria and inviting challenge. Designed for discussion mode — never just outputs a table, always defends placements and surfaces where MoSCoW is the wrong framework. Use after OST when shaping a feature, or directly when you have a solution list and need to negotiate scope.
Build an Opportunity Solution Tree following Teresa Torres' Continuous Discovery format, pragmatic variant — allows inferred opportunities marked as hypotheses when evidence is thin. Takes a JTBD canvas plus context and produces a tree with desired outcome, clustered opportunities, candidate solutions, and assumption tests for the riskiest paths. Use after JTBD when shaping a feature, or directly when an outcome is already clear.
Produce a Monday-morning standup-style recap of the previous week's merged work, drawn from git history, GitHub PRs, and linked GitHub Issues. Output is technical-but-narrative — the way a tech lead would brief their PM. Groups work by product area, anchors each item to its issue/epic title where one exists, and explains the problem each merge solved. Use on Monday mornings or when catching up after time away. Default window is the previous 7 days.
Scaffold this repo with the Builders Camp Claude OS (CLAUDE.md, skills, standards, registries). Use for new projects.
Full architecture, code quality, tests, and performance audit for large changes.
| name | merge |
| description | Safe PR merge with check verification, post-merge cleanup, and migration reminder. |
| disable-model-invocation | true |
| allowed-tools | Read, Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr merge *), Bash(gh pr diff *), Bash(git fetch *), Bash(git checkout *), Bash(git pull *), Bash(git branch *), Bash(supabase migration list *), Bash(supabase db push *) |
| argument-hint | [PR number — defaults to current branch's PR] |
Use only when the user explicitly asks to merge a PR. Never auto-trigger.
Resolve the target PR:
gh pr view --json number).Pre-merge gate (gh pr view <num> --json state,mergeStateStatus,mergeable,statusCheckRollup,baseRefName):
OPEN.mergeable must be MERGEABLE. If CONFLICTING, stop and tell the user to rebase.mergeStateStatus:
CLEAN / UNSTABLE / HAS_HOOKS → proceed (UNSTABLE is acceptable when only known-ignored checks fail; flag which ones).BLOCKED → stop. Print which required check or review is blocking. Do not bypass.BEHIND → stop. Tell the user to update the branch from base.DIRTY → stop. Conflicts.statusCheckRollup: list any failing or pending checks. Required checks must pass before merging. Known-ignored checks (per memory or user instruction) can be tolerated — call them out explicitly.Merge: gh pr merge <num> --squash --delete-branch.
--merge or --rebase if the user explicitly asks.--auto (this skill is run on demand, not queued).--admin to bypass branch protection unless the user explicitly authorizes.Verify the merge landed: gh pr view <num> --json state,mergedAt,mergeCommit. If state != MERGED, stop and report.
Post-merge cleanup:
git fetch origin.main (or the PR's base branch): git checkout <base>.git pull --ff-only.git branch -d <branch>. Skip if it has unmerged work locally.Migration reminder — if the merged diff includes any file under supabase/migrations/:
supabase migration list --linked and check whether each new file is already applied on remote.supabase db push --linked. Confirm one-by-one in the printed plan.Output a merge summary.
Output: PR: # — Merge commit: <sha> Branch deleted: <branch> (remote + local) Migrations applied: <list, or "none in diff"> Watch: <Vercel deploy URL or other monitor target if known, else "production deploy via main"> Rollback: revert merge commit on GitHub, or git revert -m 1 <sha> then push.