post_merge_setup

Execute the configured post-merge script and reconcile workflows with the .replit configuration.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/mecolejr/EVL-mOC5 --skill post-merge-setup-mecolejr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post_merge_setup
Source: https://github.com/mecolejr/EVL-mOC5/tree/main/.local/skills/post_merge_setup
Command: npx skills add https://github.com/mecolejr/EVL-mOC5 --skill post-merge-setup-mecolejr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After task merges, teams must manually run setup steps and reconcile active workflows with the project state. This Skill automates the post-merge setup and subsequent workflow reconciliation to keep environments consistent.

Core Features & Use Cases

  • Post-merge setup: executes the configured script from the project root to install dependencies, run migrations, and rebuild.
  • Workflow reconciliation: aligns running workflows with the current .replit configuration by stopping removed workflows and restarting active ones.
  • Observability and safety: includes timeout handling and non-interactive execution to prevent prompts or hangs.

Quick Start

Configure the post-merge script path in the repository settings and run the post-merge setup to execute the script and reconcile workflows.

Frequently Asked Questions about post_merge_setup

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

FAQPage Schema
What is workflow reconciliation after a task merge?

Workflow reconciliation aligns running workflows with the current configuration by stopping removed workflows and restarting active ones. This ensures your environment stays consistent after task merges without manual intervention.

Does post-merge setup require specific repository configuration settings?

To configure a post-merge script, define the scriptPath and timeout in your repository settings. The script executes non-interactively from bash with stdin closed to prevent prompts or hangs during the runPostMergeSetup flow.

What is the best way to stop removed workflows and restart active ones after a merge?

Timeout handling prevents hangs by using a defined timeout setting in the repository configuration and closing stdin during non-interactive bash execution. This ensures the post-merge script stops safely if it stalls.

How do I handle hangs when running post-merge scripts non-interactively?

The best way to reconcile workflows is using automated post-merge setup that aligns running workflows with the current configuration, stopping removed workflows and restarting active ones to maintain environment consistency.