Receber por email
← Voltar para o catálogo

pr-merge-base

Mescla uma ou mais PRs na branch base com sequenciamento tipo fila e resolução de conflitos. Use ao mesclar PRs que podem entrar em conflito entre si ou com a base, exigindo aplicação ordenada e tratamento inteligente de conflitos.

27estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add OutlineDriven/odin-claude-plugin

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/pr-merge-base/svg)](https://www.skillteca.com.br/skills/pr-merge-base)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Smart Merge to Base Branch

Merge one or more PRs into the base branch (main/master) using queue-like sequencing.

Process

  1. Detect base branch: Identify the default branch (main, master, or repo-specific) via git remote show origin or repo conventions.
  1. Enumerate PRs: List all PRs to merge. For each, fetch the latest HEAD.
  1. Create checkpoint: Record the current base branch tip as a rollback point.

`` CHECKPOINT=$(git rev-parse HEAD) ``

  1. Create integration branch: Work on a temporary branch to validate before touching base.

`` git checkout -b merge-queue/<timestamp> <base> ``

  1. Determine merge order:
  2. If the user specifies an order, use that.
  3. Otherwise, compute dependency/topological order (if PR B depends on PR A, merge A first).
  4. If PRs are independent with no clear ordering, present the list and ask the user to confirm or reorder before proceeding.
  1. Sequential merge with conflict handling — for each PR in order:

a. Attempt git merge --no-ff <pr-branch> into the integration branch. b. If merge succeeds cleanly, continue to next PR. c. If conflicts occur:

  • Analyze each conflict file using difft and codebase context.
  • Apply resolution using structural understanding (prefer base for formatting, PR for logic).
  • If a conflict cannot be resolved with confidence, abort this merge (git merge --abort), stop and report the conflict to the user with both sides and a recommended resolution.

d. After each successful merge, verify the build still passes (if build commands are available).

  1. Validate integration branch: Once all PRs are merged on the integration branch, run full build/test suite if available.
  1. Report results: Present the validated integration branch to the user. Do NOT advance the base branch automatically — only update base if the user explicitly requests it.
  1. Abort conditions — stop the queue and report if:
  2. A conflict cannot be safely auto-resolved.
  3. A post-merge build/test fails.
  4. A PR has been superseded or closed.

Roll back: git checkout <base> && git branch -D merge-queue/<timestamp> — base remains untouched at checkpoint.

Output

Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason).

Compartilhar X LinkedIn