merge-baselisted

# Merge Base Branch Merge the remote base branch into the current feature branch with pre-merge analysis, intelligent conflict resolution, and a behavioral change report. **Output philosophy**: Be concise. Show summaries, not diffs or source code. The user will ask for details if they want them. Never dump raw diffs, full file contents, or initial state unless explicitly requested. ## Phase 1: Sync with Remote Fetch all remotes and pull tracked branch changes (merge mode, never rebase). ```bash CURRENT_BRANCH=$(git branch --show-current) TRACKING=$(git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "") git fetch --all --prune if [ -n "$TRACKING" ]; then git pull --no-rebase fi ``` If the pull produces conflicts, resolve them (see Phase 4) before continuing. ## Phase 2: Identify the Base Branch Determine the base branch from PR metadata using the `git-and-github` skill: ```bash BASE_BRANCH=$(gh pr view --json baseRefName -q .baseRefName 2>/dev/null) ``` If no PR exists, fall back to the repo default branch: ```bash BASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@') ``` If neither works, ask the user. Use `origin/$BASE_BRANCH` (the remote-tracking ref, already updated by fetch) for the merge — not the local base branch, which may be stale. ## Phase 3: Pre-Merge Analysis Understand both sides of the merge internally. Read the diffs and logs to build context for conflict resolution and behavioral analy