post_merge_setup

Run post-merge setup scripts and reconcile workflows after code merges.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Celia-12/Proyecto-Mern --skill post-merge-setup-celia-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post_merge_setup
Source: https://github.com/Celia-12/Proyecto-Mern/tree/main/frontend/.local/skills/post_merge_setup
Command: npx skills add https://github.com/Celia-12/Proyecto-Mern --skill post-merge-setup-celia-12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the routine work that must occur immediately after merging changes by running a project-defined setup script and reconciling running workflows with repository configuration, reducing broken builds and stale workflows.

Core Features & Use Cases

  • Config management: Read and update post-merge script path and timeout values stored in repository configuration.
  • Automated execution: Run the configured post-merge script from the project root with stdin closed and capture stdout/stderr, duration, and exit status.
  • Workflow reconciliation: Stop workflows removed from configuration and restart or sync workflows that should be running.
  • Use Case: When dependencies change after a merge, run the post-merge script to install packages, run migrations, and rebuild, then reconcile workflows so CI state matches the updated configuration.

Quick Start

Use the post_merge_setup skill to run the configured post-merge script and show the last lines of stdout and stderr logs.

Frequently Asked Questions about post_merge_setup

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

FAQPage Schema
How do I automate setup scripts and workflow reconciliation after a code merge?

Post-merge setup automation runs a project-defined script from the repository root to install packages, run migrations, and rebuild, then reconciles active workflows with repository configuration to prevent broken builds and stale CI state.

What is workflow reconciliation in CI/CD and when do I need it?

Workflow reconciliation stops workflows removed from configuration and restarts or syncs workflows that should be running after a code merge. You need it when repository configuration changes and your CI state must match the updated setup.

How do I capture stdout, stderr, and exit status from a post-merge setup script?

Post-merge setup execution runs the configured script with stdin closed and captures stdout, stderr, runtime duration, and exit status. It returns execution status and explicit setup or reconciliation errors for debugging and retry logic.

Can I configure timeout values and script paths for post-merge automation?

Config management reads and updates the post-merge script path and timeout values stored in repository configuration. This allows you to specify which setup script runs from the project root and how long it can execute before timing out.

Why does my CI workflow break after merging dependency changes?

CI workflows break after merges when dependency changes require installs or migrations that do not run automatically. Post-merge setup scripts execute these updates and reconcile workflows so the CI state matches the updated repository configuration.

What are the limitations of automated post-merge workflow reconciliation?

Reconciliation limitations include explicit setup or reconciliation errors returned when scripts fail or timeout. The configured timeout value bounds execution, and captured stderr logs provide debugging information for retry logic when workflows cannot sync.