resolve-merge

Merge origin/main into the current branch and resolve conflicts.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill resolve-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-merge
Source: https://github.com/jamesc/skills/tree/main/skills/resolve-merge
Command: npx skills add https://github.com/jamesc/skills --skill resolve-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of updating your current branch with the latest changes from the main branch and resolving any merge conflicts that arise, ensuring your codebase stays synchronized and functional.

Core Features & Use Cases

  • Automatic Branch Update: Fetches the latest changes from origin/main and merges them into your active branch.
  • Conflict Detection & Resolution: Identifies merge conflicts and provides a structured approach to resolving them based on predefined strategies.
  • CI Verification: Runs the full Continuous Integration pipeline after resolution to ensure code integrity.
  • Use Case: When working on a feature and needing to incorporate recent updates from main, this skill handles the merge and conflict resolution, preventing integration issues.

Quick Start

Use the resolve-merge skill to update the main branch and merge it into the current branch, resolving any conflicts.

Frequently Asked Questions about resolve-merge

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

FAQPage Schema
How do I resolve Git merge conflicts automatically when updating my feature branch?

To resolve Git merge conflicts automatically, fetch the latest changes from origin/main and merge them into your current branch. The skill analyzes conflicts and applies predefined resolution strategies for code, documentation, and dependencies to ensure successful integration.

What is the best way to merge main into a current branch without breaking the CI pipeline?

The best way to merge main into a current branch while preserving CI integrity is to resolve conflicts using predefined strategies, then execute the full continuous integration pipeline via `just ci` to verify codebase functionality before pushing the resolved merge.

How does automated conflict resolution handle different types of files like code and documentation?

Automated conflict resolution handles different file types by applying predefined strategies tailored to code, documentation, and dependencies. This structured approach analyzes the specific conflict context to determine the correct resolution path for each file category.

Can I use this merge resolution skill if my project relies on continuous integration verification?

Yes, you can use this merge resolution skill if your project relies on continuous integration. It explicitly verifies code integrity by running your full CI pipeline with `just ci` after resolving conflicts and before pushing the updated branch.

What should I do if my Git branch is out of sync with the main repository?

If your Git branch is out of sync with the main repository, fetch origin/main and merge it into your active branch. This updates your codebase with the latest changes and resolves any resulting merge conflicts automatically.

Does automated Git merge resolution replace the need for manual conflict review?

Automated Git merge resolution does not entirely replace manual review for complex logic, but it handles standard conflicts in code, documentation, and dependencies using predefined strategies. It then validates the overall integrity through CI verification before pushing.