kf-conflict-resolver

Resolve git merge conflicts during push or pull sync operations.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-conflict-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kf-conflict-resolver
Source: https://github.com/Kiloforge/kiloforge-skills/tree/main/kf-conflict-resolver
Command: npx skills add https://github.com/Kiloforge/kiloforge-skills --skill kf-conflict-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve git merge conflicts that arise during push or pull sync operations by fetching remote changes, merging, resolving conflicts intelligently, and escalating when conflicts are ambiguous or high-risk.

Core Features & Use Cases

  • Automated conflict resolution for text-based source files with deterministic merging strategies
  • Escalation to a user when conflicts are ambiguous or high-risk
  • Completion of the sync after a successful merge, with clear reporting

Quick Start

Invoke the command /kf-conflict-resolver push main to start resolving conflicts during a push operation.

Frequently Asked Questions about kf-conflict-resolver

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

FAQPage Schema
How do I resolve git merge conflicts during a push or pull sync?

Resolve git merge conflicts by fetching remote changes, performing a merge, and applying deterministic strategies to text-based source files. The process completes the sync automatically and reports the results clearly.

When do I need user-guided escalation for ambiguous merge conflicts?

User-guided escalation for merge conflicts is required when conflicts are ambiguous or high-risk. The automated workflow detects these complex divergence scenarios and escalates them to the user for manual resolution.

Does the automated conflict resolution work with standard git workflows?

Automated conflict resolution works with standard git workflows by parsing direction and remote-branch arguments, verifying local git state, checking remote reachability, and validating a clean merge before completing the sync.

Can I use this to handle version-control conflicts for text-based source files?

Yes, you can handle version-control conflicts for text-based source files using deterministic merging strategies. It fetches remote changes and merges local and remote histories that diverge during push or pull operations.

What are the limitations of automated git conflict resolution?

Automated git conflict resolution is limited to text-based source files with deterministic strategies. Ambiguous or high-risk conflicts cannot be resolved automatically and require user-guided escalation to complete the sync safely.

What is the best way to automate merge conflict handling for remote branch sync?

The best way to automate merge conflict handling is to invoke a targeted command specifying the sync direction and remote branch, allowing the system to fetch, merge, resolve, and validate the clean state automatically.