land
Land the current PR by resolving merge conflicts, handling feedback, waiting for checks, and squash-merging when the branch is ready.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Land the current PR by resolving merge conflicts, handling feedback, waiting for checks, and squash-merging when the branch is ready.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when any Mister Smith request touches Linear, GitHub PR flow, packet slicing, review state, workspace hygiene, or bootstrap readiness and needs the correct Smith MCP route first.
Use after a Mister Smith SpecKit packet has been created and needs post-spec closure: packet verification, git closure, Linear materialization, honest execution-lane preparation, and follow-on execution readiness without implementation unless explicitly requested.
Use when the user wants a complete Mister Smith live runtime session or workflow evaluation with real execution, durable evidence capture, and honest task/session/autonomy proof instead of mock-only validation.
Use when Mister Smith needs spec-only frontier packet work: turning current repo truth or a pre-SpecKit primer into a new product-side SpecKit packet, or running the full local SpecKit authoring chain for an already chosen packet. Trigger for requests to create or extend a Mister Smith packet spec, pre-SpecKit primer, specify-init prompt, or full spec bundle without implementation.
Use when a Mister Smith SpecKit phase or tasks pack needs to be turned into deterministic Linear slices, blocker chains, prep-slice opportunities, and direct-execution-ready work.
Legacy-named skill for Mister Smith tasks that span Linear control-plane state, GitHub PR flow, local repo truth, lifecycle recovery, or workspace hygiene.
| name | land |
| description | Land the current PR by resolving merge conflicts, handling feedback, waiting for checks, and squash-merging when the branch is ready. |
Use this skill when a Symphony issue moves to Merging.
origin/main.origin/main checkpoint after merge.gh is installed and authenticated.Identify the PR for the current branch.
Rerun the current scope's validation before any final push.
Check mergeability:
gh pr view --json number,title,body,mergeable,urlIf the PR conflicts with main, run the pull skill, resolve conflicts, revalidate, and push.
Review open PR feedback:
Treat every actionable review comment as blocking until it is addressed in code or explicitly pushed back on with rationale.
Wait for checks:
gh pr checks --watchIf checks fail:
gh pr checks and gh run view --logWhen all checks are green and feedback is resolved, squash-merge:
gh pr merge --squash --subject "$pr_title" --body "$pr_body"After merge, run:
git fetch origin --prune
branch=$(git branch --show-current)
git switch -C main origin/main
if [ "$branch" != "main" ]; then git branch -D "$branch"; fi
scripts/verify_worktree_closure.sh
Done is not honest until the post-merge workspace cleanup is complete.