git-merge-into

Merge feature branches into a target branch and push it to remote.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/glhewett/public-skills --skill git-merge-into
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-merge-into
Source: https://github.com/glhewett/public-skills/tree/main/git-merge-into
Command: npx skills add https://github.com/glhewett/public-skills --skill git-merge-into

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge a completed feature branch into a target branch while ensuring the target is up-to-date, preventing accidental loss of work, and surfacing merge conflicts for manual resolution.

Core Features & Use Cases

  • Pre-merge validation: Checks for uncommitted changes and warns before proceeding.
  • Safe merge flow: Checks out the target branch, pulls the latest changes, performs a --no-ff merge from the current branch, and pushes the updated target branch.
  • Conflict detection and reporting: Detects merge conflicts and stops to present conflict details instead of attempting automatic resolution.
  • Use Case: A developer finishing a feature can prepare and merge their feature branch into develop or main while ensuring the target is synchronized and conflicts are handled explicitly.

Quick Start

Merge the current feature branch into develop, ensure no uncommitted changes, and push the develop branch to the remote repository.

Frequently Asked Questions about git-merge-into

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

FAQPage Schema
How do I safely merge a feature branch into a target branch and push it?

To safely merge and push a feature branch, this workflow checks out the target, pulls latest changes, and performs a --no-ff merge before pushing the updated target branch to the remote repository.

What happens if there are uncommitted changes before starting a git merge?

If uncommitted changes exist before a git merge, pre-merge validation detects them and warns you before proceeding, preventing accidental loss of work during the branch integration process.

How are merge conflicts handled during a feature branch integration?

During feature branch integration, merge conflict detection stops the process and presents conflict details for manual resolution instead of attempting automatic resolution, ensuring conflicts are handled explicitly.

Why use a --no-ff merge when finalizing feature work in git?

Using a --no-ff merge when finalizing feature work in git ensures the target branch records a merge commit, preserving the historical context of the feature branch instead of linearizing the commits.

Can I synchronize a target branch with remote before merging my feature work?

Yes, you can synchronize a target branch with remote before merging feature work; the process checks out the target branch and pulls the latest changes to ensure it is up-to-date prior to the merge.