cmd-pr-conflict-resolver

Classify and resolve code merge conflicts using a 3-tier system.

8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-conflict-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-pr-conflict-resolver
Source: https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-pr-conflict-resolver
Command: npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-conflict-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, systematic approach to resolving merge conflicts in code, ensuring that resolutions are context-aware, well-reasoned, and safely integrated.

Core Features & Use Cases

  • Systematic Conflict Mapping: Identifies and inventories all merge conflicts.
  • Contextual Analysis: Gathers context by examining file history, surrounding code, and business logic impact for each conflict.
  • 3-Tier Classification: Categorizes conflicts into Auto-resolve, Resolve with Rationale, or Escalate tiers.
  • Guided Resolution: Provides specific strategies for resolving different types of conflicts (e.g., lists, function bodies, configs).
  • Safe Verification & Staging: Ensures all conflicts are resolved without markers and staged appropriately.
  • Use Case: When faced with a complex merge involving multiple developers and overlapping changes, this Skill guides you through each conflict, ensuring no critical logic is lost or incorrectly applied.

Quick Start

Use the cmd-pr-conflict-resolver skill to systematically resolve all merge conflicts in the current branch.

Frequently Asked Questions about cmd-pr-conflict-resolver

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

FAQPage Schema
How do I systematically resolve git merge conflicts in a multi-developer branch?

Systematically resolve merge conflicts by mapping each conflict, analyzing surrounding code and commit history, classifying it into a 3-tier system, and applying targeted resolution strategies before staging. This structured approach ensures context-aware resolutions without losing critical business logic.

What is the best way to handle complex code resolution for overlapping git changes?

The best way to handle complex code resolution is to use a 3-tier classification system that categorizes conflicts into auto-resolve, resolve with rationale, or escalate, ensuring safe verification and staging. This prevents incorrectly applied logic during complex merges.

How does contextual analysis work when resolving version control merge conflicts?

Contextual analysis for merge conflicts works by examining file history, surrounding code, and business logic impact to build context for each conflict. This context informs whether a conflict can be auto-resolved or requires explicit rationale.

When should I escalate merge conflicts instead of auto-resolving them?

You should escalate merge conflicts when contextual analysis of commit history and surrounding code indicates complex business logic changes that cannot be safely auto-resolved. The 3-tier system classifies these high-risk conflicts for manual review.

Can I use this approach to resolve conflicts in function bodies and configuration files?

Yes, you can resolve conflicts in function bodies and configuration files using guided resolution strategies tailored to different conflict types. The system verifies all conflict markers are removed and ensures files are safely staged.

Does this merge conflict resolution method work without additional developer tools or dependencies?

Yes, this merge conflict resolution method works without additional dependencies, relying solely on analyzing commit history and surrounding code context. It systematically inventories conflicts and safely stages resolved files natively.