merge

Merge Git branches with context-aware conflict resolution from pull request details.

Updated Aug 6, 2025
One-click install
npx skills add https://github.com/flosrn/.claude --skill merge-flosrn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/flosrn/.claude/tree/main/skills/git-merge
Command: npx skills add https://github.com/flosrn/.claude --skill merge-flosrn

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the Git merging process by providing context-aware conflict resolution, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated Conflict Detection: Identifies merge conflicts automatically.
  • Context-Aware Resolution: Uses PR/issue context to intelligently resolve conflicts.
  • Branch Merging: Facilitates merging feature branches into main branches.
  • Use Case: When merging a new feature branch, this Skill can automatically resolve common conflicts by understanding the intent of the changes from the associated pull request.

Quick Start

Use the merge skill to merge the 'feature-x' branch into the current branch.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I resolve Git merge conflicts automatically using pull request context?

Git merge conflicts can be resolved automatically by analyzing pull request details and issue descriptions to understand change intent. This approach intelligently resolves conflicts by applying context-aware rules for different file types like package.json and source code during the branch merge.

What is context-aware conflict resolution when merging Git feature branches?

Context-aware conflict resolution is a merging mechanism that uses PR and issue descriptions to understand the intent behind changes. It identifies conflicts automatically and applies specific rules for handling different file types like package.json and source code to efficiently resolve them.

How do I merge a Git feature branch into main while detecting and verifying conflicts?

Merging a Git feature branch involves automated fetching, merging, conflict detection, and verification steps. The process analyzes pull request context to intelligently resolve conflicts for various file types, reducing manual effort and potential errors during the branch merge.

Can I resolve package.json conflicts differently than source code during a Git merge?

Yes, Git merge conflict resolution can apply specific rules for handling different file types like package.json and source code. By analyzing pull request details, the merge process intelligently resolves conflicts based on the specific file type and the intent of the changes.

Does automated Git branch merging require manual conflict resolution for common issues?

Automated Git branch merging reduces manual conflict resolution by using pull request and issue context to intelligently resolve common conflicts. It supports automated fetching, merging, conflict detection, and verification, handling different file types like package.json and source code efficiently.