merge-assist

Plan human-approved cherry-pick integrations with confirmation gates before execution.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill merge-assist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-assist
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/merge-assist
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill merge-assist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Selective, human-approved branch integrations without automatic merging, ensuring deliberate changes are gated by explicit confirmations.

Core Features & Use Cases

  • Enforces a human-in-the-loop for every gate in the merge flow (branch selection, inspection, planning, and execution).
  • Provides a structured plan for cherry-pick or manual port operations, with safety checks and clear failure handling.
  • Use cases include moving a feature from a feature branch to main while avoiding unintended changes or regressions.

Quick Start

Start a merge-assist session to outline the target and source branches, inspect candidate commits, and generate a plan for gated execution.

Frequently Asked Questions about merge-assist

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

FAQPage Schema
How do I perform a guarded git merge with human approvals?

A guarded git merge requires a multi-step process with confirmation gates, branch verification, commit selection, plan creation, and explicit human execution prompts, ensuring no git operations run until approved.

What is the best way to cherry-pick commits between branches safely?

Cherry-picking commits safely involves a structured plan with safety checks, branch verification, and clear failure handling, enforcing human-in-the-loop gate confirmations for every step without automated merges.

Can I port specific commits from a feature branch to main without automated merges?

Yes, you can resolve selective, human-approved branch integrations by generating a gated execution plan that inspects candidate commits and requires explicit confirmation before any port operations occur.

Why do I need human-in-the-loop confirmation gates for branch integrations?

Human-in-the-loop confirmation gates prevent unintended changes or regressions by enforcing deliberate branch selection, inspection, planning, and execution steps before any git operations are performed.

Does merge-assist work without dependencies or external components?

Yes, merge-assist operates with zero dependencies and no external components, functioning purely as a guided session to outline target and source branches, inspect commits, and generate a gated execution plan.