git-magic

Sync a feature branch with origin/main, resolve conflicts, and prepare a PR description.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/wapgear/izmailov-skills --skill git-magic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-magic
Source: https://github.com/wapgear/izmailov-skills/tree/main/skills/git-magic
Command: npx skills add https://github.com/wapgear/izmailov-skills --skill git-magic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync a feature branch with latest main, resolve conflicts, commit current work, push the branch, and create a pull request with a repo-matched description.

Core Features & Use Cases

  • Automated branch syncing: fetches latest main, merges into the feature branch, and prepares a PR-ready description.
  • Conflict resolution guidance: identifies conflicts and suggests minimal, correct edits with preservation of intent.
  • PR creation ready: pushes the branch and opens a PR with a coherent summary aligned to the repo description.

Quick Start

Merge origin/main into your branch, resolve conflicts, push, and open a pull request with a descriptive message.

Frequently Asked Questions about git-magic

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

FAQPage Schema
How do I sync a feature branch with main and resolve merge conflicts?▼

To sync a feature branch with main, the workflow fetches the latest origin/main, merges it into your branch, and applies deterministic steps to resolve merge conflicts while preserving your original intent before pushing.

How do I automatically create a pull request after merging main into my branch?▼

You can automatically create a pull request by pushing your synced feature branch, which triggers the generation of a coherent PR description matched to your repository's context for immediate review.

What is the best way to automate branch syncing before opening a pull request?▼

Automating branch syncing involves fetching the latest main, merging it into the feature branch, resolving any conflicts with minimal edits, and committing the changes to prepare a patch-ready PR.

Does this branch syncing workflow include guardrails for conflict resolution?▼

Yes, the branch syncing workflow implements safety rules and guardrails during the merge process to ensure conflict resolution suggests minimal, correct edits while maintaining the feature's intended logic.

Can I prepare a PR-ready description directly from a diverged feature branch?▼

Yes, you can prepare a PR-ready description from a diverged branch by merging origin/main, resolving conflicts, and pushing the updated branch to generate a coherent pull request summary.