Verified:GitHub

merge-completed-work

Merge completed GitLab branches into parent branches after verifying issue closure.

1|Updated Jan 30, 2026

Search Tags:#git #workflow automation #branching #code integration #gitlab #merge request

One-click install

npx skills add https://github.com/Capplequoppe/agent-studio --skill merge-completed-work

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: merge-completed-work
Source: https://github.com/Capplequoppe/agent-studio/tree/main/.claude/skills/merge-completed-work
Command: npx skills add https://github.com/Capplequoppe/agent-studio --skill merge-completed-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the process of merging completed development branches into their respective parent branches, streamlining the workflow for managing epics, phases, and plans.

Core Features & Use Cases

Automated Branch Merging: Merges phase branches into plan branches, epic branches into master, and plan branches into master.
Intelligent Branch Identification: Determines source and target branches based on argument type (epic IID or plan name) and GitLab labels.
Readiness Verification: Ensures all associated issues are closed and dependent branches are merged before creating a merge request.
Use Case: After completing all tasks for a specific phase of a project, this skill can automatically create a merge request to integrate that phase's work into the main project plan branch.

Quick Start

Use the merge-completed-work skill to merge the completed epic with IID 123 into its parent branch.

Frequently Asked Questions about merge-completed-work

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

FAQPage Schema

How do I automate merging completed GitLab branches into their parent branches?▼

You can automate merging completed GitLab branches by using a workflow that identifies phase, epic, and plan branches, verifies issue completion, and creates merge requests into the correct parent branches automatically.

Can I merge a GitLab epic branch into master using its IID?▼

Yes, you can merge a GitLab epic branch into master by providing the epic IID. The system uses the IID and GitLab labels to identify the correct source and target branches before creating the merge request.

What is the best way to verify all issues are closed before merging a phase branch?▼

The best way to verify issue completion before merging a phase branch is to use an automated readiness check that ensures all associated issues are closed and dependent branches are merged prior to creating a merge request.

How do I create a merge request to integrate a completed project phase into a plan branch?▼

To integrate a completed phase into a plan branch, you trigger an automated merge process that uses GitLab labels to identify the phase and plan branches, verifies readiness, and generates a merge request with appropriate titles and descriptions.

Does this automated merge workflow support branching by plan name instead of epic IID?▼

Yes, the automated merge workflow supports identifying branches by plan name as well as by epic IID, determining the source and target branches based on the provided argument type and associated GitLab labels.

Why should I verify branch readiness before merging completed work in GitLab?▼

You should verify branch readiness before merging completed work to prevent integrating incomplete features. The verification process checks that all dependent branches are merged and associated issues are closed before creating the merge request.