prepare-merge

Generate a merge-prep plan with documentation and changelog updates.

1|Updated Aug 21, 2025
One-click install
npx skills add https://github.com/camronh/EZVals --skill prepare-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-merge
Source: https://github.com/camronh/EZVals/tree/main/.agents/skills/prepare-merge
Command: npx skills add https://github.com/camronh/EZVals --skill prepare-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare documentation updates before merging a feature branch to ensure consistency across docs and changelogs, reducing manual overhead.

Core Features & Use Cases

  • Generate a step-by-step merge-prep plan that analyzes changes.
  • Update documentation and changelog entries in the target branch.
  • Provide a final merge command and a summary of actions taken for auditing.

Quick Start

Specify a target branch and generate a merge-prep plan that analyzes changes, updates docs and changelog, and outputs the final merge command.

Frequently Asked Questions about prepare-merge

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

FAQPage Schema
How do I automate changelog updates before a git branch merge?

You can automate changelog updates by analyzing git history and diffs from a feature branch to generate consistent documentation entries. This process creates a merge-prep plan that updates docs and outputs a final merge command for code review.

What is a merge-prep workflow in software engineering?

A merge-prep workflow is a pre-merge process that prepares documentation and changelog updates for a feature branch. It analyzes git history, generates an audit summary of changes, and ensures consistency across docs to reduce manual overhead during release workflows.

How do I generate a merge command and summary from a git diff?

Generate a merge command and summary by providing a target branch input for diff analysis. The workflow evaluates branch changes, updates the changelog, and produces a final merge command alongside an action summary for release auditing.

Do I need to specify a target branch to prepare documentation updates for a merge?

Yes, specifying a target branch is required to prepare documentation updates for a merge. The target branch input drives the git history and diff analysis, which generates the changelog updates and the final merge command.

Can I use automated merge prep for code review workflows?

Yes, automated merge prep applies directly to code review workflows. It generates a step-by-step plan that analyzes changes, updates changelog entries, and provides a summary of actions taken for consistent documentation during release workflows.