메뉴
Merge a green ZenUML web-sequence PR into master and verify staging CI after merge. Use when the user says "land PR", "merge this", "merge", "land", or a PR is ready to merge. Does not publish a production GitHub release.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Take the current ZenUML web-sequence branch from local validation through PR submission, green CI, and merge to master. Use when the user says "ship", "ship it", "ship this branch", "submit and merge", or wants the full branch-to-master workflow. Stops at first failure and does not deploy production.
Push the current ZenUML web-sequence branch, create or reuse a GitHub PR against master, then always run babysit-pr until CI is green or blocked. Use when the user says "submit", "create PR", "open a pull request", "push and PR", or wants to publish branch work without merging. Does not merge — use land-pr after babysit passes.
Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate. Use when the user says "babysit PR", "check PR status", "fix CI", "why is CI red", "watch this PR", or a PR is blocked by build, release, Firebase deploy, artifact, lint, test, or runner failures.
Release ZenUML web-sequence to production (app.zenuml.com) by publishing a GitHub release, wait for deploy-prod CI + @smoke, then run a release-delta spot check (spot-check skill Step 5.5). Use when the user says "release", "release app", "deploy to prod", "ship to production", or invokes /release-app. Does not merge PRs — use ship-branch first if there are pending changes on a feature branch.
Ad hoc, AI-driven verification of a specific behavior on ZenUML web-sequence — not a new checked-in E2E test. Use after developing a feature, fixing a bug, validating a branch, checking staging, or post-release on app.zenuml.com. Drives Playwright (CLI or MCP) against the live app and #demo-frame preview. Triggers on "spot check", "run a spot check on X", "spot check this fix", "spot check on staging", "spot check staging.zenuml.com", "verify on prod".
Run local validation checks for ZenUML web-sequence before pushing, opening a PR, or merging. Use when the user says "validate", "check branch", "run tests", "preflight", "is this ready", or before submit-branch or ship-branch. Covers Yarn/Vite/Jest/Playwright checks, build/release risk, and spot-check plans for UI/diagram changes (see spot-check skill).
| name | land-pr |
| description | Merge a green ZenUML web-sequence PR into master and verify staging CI after merge. Use when the user says "land PR", "merge this", "merge", "land", or a PR is ready to merge. Does not publish a production GitHub release. |
Merge a green PR into master and verify the post-merge staging workflow.
The Deploy to Stage workflow runs on push and pull_request. On master, it builds, packages release artifacts, configures Firebase staging, deploys staging, and uploads the Chrome extension artifact.
Production deploy is separate: publishing a GitHub release triggers Deploy to Prod.
Resolve the PR number, then run:
gh pr view <PR_NUMBER> --repo ZenUml/web-sequence --json state,isDraft,mergeable,reviewDecision,statusCheckRollup,headRefName,baseRefName,url
Verify:
master.If checks are not green, use babysit-pr or stop and report.
Use the repo's allowed merge strategy instead of assuming squash:
MERGE_FLAG=$(gh api repos/ZenUml/web-sequence \
--jq 'if .allow_squash_merge and (.allow_merge_commit | not) and (.allow_rebase_merge | not) then "--squash"
elif .allow_rebase_merge and (.allow_merge_commit | not) and (.allow_squash_merge | not) then "--rebase"
else "--merge" end')
gh pr merge <PR_NUMBER> --repo ZenUml/web-sequence --auto --delete-branch $MERGE_FLAG
If the user requested a specific merge method, use it only if GitHub allows it.
Poll until merged:
gh pr view <PR_NUMBER> --repo ZenUml/web-sequence --json state,mergeCommit
If auto-merge remains armed but not merged, report what is blocking it.
After merge:
gh run list --repo ZenUml/web-sequence --branch master --limit 5 --json databaseId,name,status,conclusion,createdAt,event
gh run watch <RUN_ID> --repo ZenUml/web-sequence
Check the Deploy to Stage result. If it fails after merge, do not auto-revert. Report the run URL, failing job, and key log lines.
Land Report: PR #<number>
- Merge: MERGED|BLOCKED|AUTO-MERGE ARMED
- Merge commit: <sha>
- Master staging CI: PASS|FAIL|PENDING
- Production: not deployed; publish a GitHub release to trigger Deploy to Prod
babysit-pr.submit-branch.