merge

Integrates a target branch into the current branch with conflict resolution and quality-gate inspection.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill merge-jhostalek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/merge
Command: npx skills add https://github.com/JHostalek/dotclaude --skill merge-jhostalek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps integrate upstream branch changes into the current branch without losing work, leaving unresolved conflicts, breaking migration chains, or bypassing repository quality gates.

Core Features & Use Cases

  • Safe Branch Integration: Merge a remote-tracking target branch into the current branch with an explicit conventional commit message.
  • Divergence Analysis: Check ahead and behind commits and detect whether a squash-merged target is already contained before choosing the merge strategy.
  • Conflict and Migration Handling: Resolve conflicts using repository-specific heuristics and reconcile migration files when both branches modify the migration chain.
  • Quality Gate Verification: Inspect and run configured hooks and repository checks before pushing the completed merge.
  • Use Case: When your feature branch needs the latest changes from the main branch, use this Skill to assess divergence, merge the remote branch, resolve conflicts, validate migrations, run quality gates, and report the result.

Quick Start

Use the merge skill to integrate the latest main branch into the current branch and resolve any conflicts.

Frequently Asked Questions about merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge a remote branch into my current branch without losing work or leaving unresolved conflicts?

To merge a remote branch safely, integrate the target branch using divergence analysis to assess ahead and behind commits, resolve conflicts using repository-specific heuristics, and validate quality gates before pushing the completed merge.

What is the best way to handle git merge conflicts when both branches modify migration files?

Handling git merge conflicts with modified migration files requires migration reconciliation, where the merge process detects dual modifications to the migration chain and applies conflict-specific decision making to preserve repository integrity.

How does squash-merge detection work when synchronizing with an upstream branch?

Squash-merge detection works by analyzing divergence between branches to check whether the squash-merged target is already contained within the current branch, ensuring the correct merge strategy is chosen before integrating upstream changes.

Can I run repository quality gates and hook validations before pushing a completed merge?

Yes, you can run repository quality gates and hook validations before pushing by inspecting configured hooks and repository checks during the merge workflow, ensuring the integrated branch passes all validation criteria.

Why do I need divergence analysis before choosing a git merge strategy?

Divergence analysis is required before choosing a git merge strategy to evaluate ahead and behind commits, preventing unnecessary merges of already contained squash-merged targets and avoiding broken migration chains during branch integration.

Does this merge process generate a report of integrated commits and resolution outcomes?

Yes, the merge process generates a structured report detailing the integrated commits and conflict resolution outcomes, providing full visibility into the branch integration and upstream synchronization results.