post_merge_setup

Run root-level bash setup scripts and reconcile .replit workflows after merges.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill post-merge-setup-naopensedoit2-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post_merge_setup
Source: https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor/tree/main/.local/skills/post_merge_setup
Command: npx skills add https://github.com/naopensedoit2-design/Claramente-nao-sou-um-Escritor --skill post-merge-setup-naopensedoit2-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken automation after merges by ensuring a deterministic post-merge setup script runs and that active workflows match the latest .replit configuration.

Core Features & Use Cases

  • Post-merge setup execution: Runs the configured bash script from the project root to install dependencies, run migrations, and rebuild.
  • Configurable timeout with fail-fast behavior: Kills the script if it exceeds the configured timeout and surfaces the failure immediately.
  • Workflow reconciliation: Stops workflows removed from .replit and restarts workflows that should be running based on the current config.
  • Use Case: After you merge a change that affects database schema or dependency graphs, you rely on this skill to apply migrations and keep background workflows consistent without manual cleanup.

Quick Start

Ask the assistant to run post-merge setup and report any setup or reconciliation errors so you can fix the script or timeout if needed.

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 database migrations and dependency updates after a git merge?

Automating database migrations after a git merge requires executing a root-level bash setup script in a deterministic environment. This skill runs your configured post-merge setup to install dependencies, apply migrations, and rebuild automatically without manual intervention.

Why does my post-merge deployment workflow break or hang indefinitely?

Post-merge workflows often break due to unmanaged script execution or missing timeouts. This skill enforces a strict configurable timeout with fail-fast behavior, killing scripts that exceed the limit and surfacing failures immediately for debugging.

How do I keep Replit workflows synced with the current configuration?

Keeping Replit workflows synced involves reconciling active processes with the `.replit` configuration. This skill stops workflows removed from `.replit` and restarts expected workflows based on the current config without requiring interactive stdin.

Can I run post-merge setup scripts without interactive terminal input?

Running post-merge setup scripts without interactive stdin is possible by executing them in a deterministic environment. This skill reads and updates post-merge configuration from `.replit` and runs `runPostMergeSetup()` to capture logs and durations autonomously.

What happens if a post-merge bash script exceeds its execution time limit?

If a post-merge bash script exceeds its configured timeout, the process is killed immediately. This fail-fast behavior surfaces the failure right away so you can fix the script or adjust the timeout parameters.