From odin
Merges multiple PRs into a temporal integration branch for staged validation before advancing the base branch, with ordered conflict resolution and build/test checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/odin:pr-merge-temporalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Merge multiple PRs into a temporal integration branch for validation before merging to base.
Merge multiple PRs into a temporal integration branch for validation before merging to base.
Detect base branch: Identify the default branch via git remote show origin or repo conventions.
Enumerate PRs: List all PRs to merge. For each, fetch the latest HEAD.
Create temporal branch: Fetch latest and branch from the remote base tip.
git fetch origin
git checkout -b temporal/<timestamp> origin/<base>
Determine merge order:
Sequential merge with conflict handling — for each PR in order:
a. Attempt git merge --no-ff <pr-branch> into the temporal branch.
b. If merge succeeds cleanly, continue to next PR.
c. If conflicts occur:
difft and codebase context.git merge --abort), stop, and report the conflict with both sides and a recommended resolution.
d. After each successful merge, run available build/test commands to catch regressions early.Validate temporal branch: Once all PRs are merged, run full build/test suite if available.
Report results: Present the validated temporal branch to the user. Do NOT merge into base automatically — only advance base if the user explicitly requests it.
Abort conditions — stop the queue and report if:
git checkout <base> — base remains untouched.Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason). Include the temporal branch name for user review.
npx claudepluginhub outlinedriven/odin-claude-plugin --plugin odinMerges multiple PRs into a base branch with queue-like sequencing and intelligent conflict resolution. Reports success, conflict details, or blockers for each PR.
Sequentially squash-merges a linear chain of stacked PRs into an epic branch, producing one squash commit per PR with dependency-ordered rebase and per-iteration user approval gates.
Discovers open batch PRs from CHANGE_RECORD.json files, analyzes conflicts, determines optimal merge order, and executes user-guided merges on GitHub or Bitbucket.