meta-merge-contributions

Review and merge skill contribution branches with semantic versioning and changelog updates.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill meta-merge-contributions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-merge-contributions
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/meta-merge-contributions
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill meta-merge-contributions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of managing distributed contributions across multiple project repositories by providing a centralized, automated workflow for reviewing, merging, and versioning skill updates.

Core Features & Use Cases

  • Contribution Review: Automatically lists and displays diffs for pending skill improvements from various project branches.
  • Automated Versioning: Enforces semantic versioning by calculating appropriate bumps based on the nature of the changes and updating the catalog.
  • Use Case: When a developer submits an improvement to a shared skill from their local project, this skill allows the maintainer to review the changes, apply them to the main repository, and trigger a clean release for all other projects.

Quick Start

Use the meta-merge-contributions skill to review and process all pending skill improvements from project branches.

Frequently Asked Questions about meta-merge-contributions

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

FAQPage Schema
How do I automate merging git contribution branches into a main repository?

Automating git contribution branch merges involves systematically reviewing diffs, integrating changes, and cleaning up branches. This skill facilitates that workflow by analyzing pending improvements, merging them into the primary repository, and synchronizing the catalog automatically.

What is the best way to manage semantic versioning for shared skill updates?

Managing semantic versioning for shared skill updates requires calculating appropriate version bumps based on change nature. This skill enforces semantic versioning by automatically determining the correct bump level and updating the changelog and catalog after integrating contributions.

How do I review and integrate distributed contributions across multiple project branches?

Reviewing distributed contributions involves listing pending changes and displaying diffs from various project branches. This skill provides a centralized workflow to display contribution diffs, process improvements, and merge them into the main repository while maintaining repository integrity.

Can I automate branch cleanup and catalog synchronization after a successful git merge?

Automating branch cleanup and catalog synchronization after a successful git merge ensures repository integrity. This skill manages the lifecycle of proposed changes by automatically removing merged branches and synchronizing the catalog once integration is complete.

Why does merging skill contributions from local projects create repository friction?

Merging skill contributions from local projects creates repository friction due to decentralized changes and manual version tracking. This skill solves that friction by providing a centralized, automated workflow for reviewing, merging, and versioning distributed skill updates.

Does this merge workflow handle changelog maintenance automatically?

This merge workflow handles changelog maintenance automatically by updating records during the integration process. It calculates semantic version bumps based on the changes applied and ensures the changelog reflects the newly merged contributions accurately.