git-rebase

Guide conservative resolution of Git merge and rebase conflicts.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/ederfmatos/claude-voice-bridge --skill git-rebase-ederfmatos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-rebase
Source: https://github.com/ederfmatos/claude-voice-bridge/tree/main/.claude/skills/git-rebase
Command: npx skills add https://github.com/ederfmatos/claude-voice-bridge --skill git-rebase-ederfmatos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide to resolving Git merge and rebase conflicts, ensuring that both sides' code changes are preserved and conflicts are resolved safely and effectively.

Core Features & Use Cases

  • Conservative Conflict Resolution: Guides the user to resolve conflicts conservatively, preserving both sides' intent.
  • Staging Resolutions: Only stages understood resolutions to maintain a clean merge result.
  • Detailed Instructions: Offers step-by-step instructions for inspecting, editing, and staging resolved files.
  • Use Case: When using Compozy for integration work, this Skill helps users to handle Git conflicts in a way that maintains code integrity and allows for an honest rollback if needed.

Quick Start

Use the git-rebase skill to resolve the Git merge conflict in your current branch.

Frequently Asked Questions about git-rebase

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

FAQPage Schema
How do I resolve Git merge conflicts while preserving both sides' code changes?

To resolve Git merge conflicts conservatively, inspect each conflicting file, manually edit to preserve both sides' intent, and stage only understood resolutions to maintain a clean merge result and code integrity.

What is the best way to handle Git rebase conflicts safely?

Handling Git rebase conflicts safely requires step-by-step inspection and editing of conflicted files, staging only understood resolutions to allow for an honest rollback if needed while preserving both branches' code changes.

When do I need a conservative approach to resolving Git merge conflicts?

A conservative approach to Git merge conflicts is needed during integration work when maintaining code integrity is critical, ensuring both sides' changes are preserved and allowing for safe rollbacks after the merge.

How do I stage resolved files during a Git rebase without losing code integrity?

Stage resolved files during a Git rebase by editing the conflicted sections to preserve both sides' intent, then staging only those understood resolutions to ensure a clean merge result and maintain code integrity.

Why does resolving Git merge conflicts conservatively allow for safe rollbacks?

Resolving Git merge conflicts conservatively allows for safe rollbacks because only understood resolutions are staged, ensuring the merge result remains clean and the codebase integrity is preserved throughout the integration work.

Do I need prior Git knowledge to resolve merge and rebase conflicts using this approach?

Yes, resolving Git merge and rebase conflicts with this approach requires an understanding of Git operations and conflict resolution strategies to safely inspect, edit, and stage resolved files while maintaining code integrity.