post_merge_setup

Run post-merge scripts and reconcile workflows against .replit configuration.

5|21|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/Exocore-Organization/exocore-web --skill post-merge-setup-exocore-organization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post_merge_setup
Source: https://github.com/Exocore-Organization/exocore-web/tree/main/.local/skills/post_merge_setup
Command: npx skills add https://github.com/Exocore-Organization/exocore-web --skill post-merge-setup-exocore-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a merge, essential setup tasks and workflow reconciliation may be missed or inconsistent, leading to broken environments and out-of-date processes.

Core Features & Use Cases

  • Automatic execution of a project-root post-merge script to install dependencies, run migrations, and rebuild.
  • Workflow reconciliation that stops removed workflows and restarts those still active to reflect the latest .replit configuration.
  • Configured timeouts and non-interactive execution with clear failure alerts to help maintain stable CI/CD workflows.

Quick Start

Configure a post-merge script at the project root and let the system run it automatically after merges.

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 post-merge environment setup and workflow reconciliation?

Automate post-merge setup by running a configured script from your project root that handles dependency installation and migrations, while reconciling active workflows against your configuration to ensure environment consistency after a merge.

Why do my workflows break or become inconsistent after a git merge?

Workflows break after a merge when essential setup tasks like dependency installation or process restarts are missed. Automating post-merge reconciliation stops removed workflows and restarts active ones to reflect the latest configuration changes.

How do I run a post-merge script non-interactively in a CI/CD pipeline?

Run a post-merge script non-interactively by configuring its path in your project configuration file. The system enforces non-interactive execution with configured timeouts and provides clear failure alerts to maintain stable CI/CD workflows.

Do I need a specific configuration file to automate post-merge workflow reconciliation?

Yes, you need a .replit configuration file in your project. The post-merge automation requires a script path defined in this configuration to automatically run setup and restart workflows after merges.

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

The best way to stop removed workflows and restart active ones is through automated workflow reconciliation. This process evaluates your latest project configuration and restarts necessary processes to mirror the current state after a merge.