메뉴
Merge this branch's target (open PR's base or repo default) into HEAD, resolve conflicts in branch context, push unless held. Use when the user asks to sync, merge main/dev/target into HEAD, or resolve merge conflicts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | sync-target |
| description | Merge this branch's target (open PR's base or repo default) into HEAD, resolve conflicts in branch context, push unless held. Use when the user asks to sync, merge main/dev/target into HEAD, or resolve merge conflicts. |
Load skills: pr-context, quality-ship, git-advanced. (worktree-setup is lazy — see §5.)
Target = where this branch lands. Precedence: explicit arg → open PR's baseRefName → repo default (origin/HEAD). Never hardcode dev/main.
CURRENT=$(git rev-parse --abbrev-ref HEAD)
REMOTE=$(git remote | head -1)
git fetch "$REMOTE" --prune
TARGET=$(printf '%s\n' $ARGUMENTS | grep -v '^--' | head -1)
[ -z "$TARGET" ] && TARGET=$(gh pr view --json baseRefName --jq .baseRefName 2>/dev/null)
[ -z "$TARGET" ] && TARGET=$(git symbolic-ref refs/remotes/"$REMOTE"/HEAD 2>/dev/null | sed "s|refs/remotes/$REMOTE/||")
If $TARGET is empty or equals $CURRENT, ask. Surface "$REMOTE/$TARGET" → "$CURRENT" and confirm — stacked PRs miscall easily.
gh pr view --json title,body,headRefName,baseRefName 2>/dev/null
git log --oneline "$REMOTE/$TARGET".."$CURRENT"
git diff --stat "$REMOTE/$TARGET".."$CURRENT"
Note: files this branch owns, what it changes, what to preserve from upstream.
git merge "$REMOTE/$TARGET" --no-edit
Clean? Skip to §5. Else capture the targeted scope for §4–§5:
CONFLICTS=$(git diff --name-only --diff-filter=U)
Hold in memory — the U filter empties after staging.
For each file in $CONFLICTS, read both sides and classify. Tag each resolution High (mechanical, clear intent) or Low (judgment call on business logic) — §6 gates on these tags.
| Type | Action |
|---|---|
| Non-overlapping | Integrate both |
| Superseding | Keep ours; adopt new deps/imports/types from theirs |
| Upstream improvement | Take theirs |
| Genuine collision | Judge from branch context |
Stage resolutions, then git commit --no-edit.
Targeted scope = $CONFLICTS — not the full merge diff. Upstream lines came in pre-validated; widening scope rebuilds packages this branch never touched.
Run quality-ship with that scope:
$CONFLICTS paths.$CONFLICTS (e.g. turbo run … --filter={<pkg>…}).Worktree repair is lazy — load worktree-setup only on Cannot find module / empty-dist/ errors for an in-scope package. Don't run verify.py proactively; its full-workspace manifest will demand artifacts (electron-forge bundles, …) outside your scope.
$ARGUMENTS may include --full-scope to opt back into whole-diff validation.
Separate commits for fixes.
Hold if any:
$ARGUMENTS contains --no-pushWhen holding: summarize each resolution + confidence; for Low ones, name the ambiguity and the choice; ask before pushing.
Otherwise:
git push -u origin HEAD
Full PR review workflows -- first-pass, deeper (overcoverage), follow-up (re-review). Load when the user invokes /review-pr or explicitly asks for a PR review, deeper wave, or re-review; never ambiently.
Shared atom for analyzing a diff and writing a structured PR description. Background knowledge for workflow commands -- not invoked directly.
Author a publication-grade single-file HTML design doc (RFCs, architecture proposals, sync prep). Editorial typography, decision cards, fact-checked code references, Playwright-verified layout, secret-gist publishing. Use when an engineer asks for a design doc, RFC, monograph, sync-prep brief, or "make this look like a real spec."
Shared atom for running quality checks, committing, and pushing. Background knowledge for workflow commands -- not invoked directly.
Self-review your aggregate diff before shipping to catch dead weight, junk code, perf misses, pattern drift, AI slop, and scope creep. Use when the user asks to scrub, stranger-review, or clean up changes prior to opening a PR.
Shared atom for structural maintainability judgment on a diff -- hunt code-judo simplifications, spaghetti-condition growth, file-size explosions, and orchestration smells. Background knowledge for review and self-review flows -- not invoked directly.