merge-main

Fetch and merge the base branch into the current feature branch.

2|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/cboone/cboone-cc-plugins --skill merge-main
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-main
Source: https://github.com/cboone/cboone-cc-plugins/tree/main/plugins/merge-main/skills/merge-main
Command: npx skills add https://github.com/cboone/cboone-cc-plugins --skill merge-main

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating your current feature branch with the latest changes from the main or base branch, automatically handling potential merge conflicts.

Core Features & Use Cases

  • Automated Fetch & Merge: Fetches the latest changes from the base branch and merges them into your current branch.
  • Conflict Resolution: Guides through resolving merge conflicts, offering options to stash, commit, or abort.
  • Use Case: When working on a long-running feature, you need to incorporate recent updates from main to avoid a large, complex merge later. This Skill handles that update smoothly.

Quick Start

Update the current branch by merging the base branch.

Frequently Asked Questions about merge-main

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

FAQPage Schema
How do I merge the main branch into my current feature branch?

To merge the main branch, this skill fetches the latest base branch changes and integrates them into your current feature branch. It automatically detects the base branch via the gh CLI or fallback methods, then pushes the merged result.

What is the best way to handle uncommitted changes before a git branch merge?

Before a git branch merge, uncommitted changes are handled by automatically stashing them or invoking a commit workflow. This ensures a clean working tree before fetching and merging the base branch updates.

How does conflict resolution work when integrating code from the base branch?

Conflict resolution during a base branch merge provides a structured workflow to guide you through resolving clashes. You can choose to stash, commit, or abort the merge if the conflicts cannot be resolved automatically.

Does this merge workflow support automatic base branch detection without manual configuration?

Yes, the merge workflow supports automatic base branch detection without manual configuration. It identifies the base branch using the gh command line tool and utilizes fallback methods if gh is unavailable.

What happens to lockfile updates after a git merge is completed?

After a git merge is completed, the workflow includes post-merge steps for lockfile updates. It ensures dependencies are synchronized before pushing the final merged feature branch to the remote repository.