postmerge

Automate post-merge verification of CI, production health, and file freshness.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill postmerge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmerge
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/postmerge
Command: npx skills add https://github.com/jikig-ai/soleur --skill postmerge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates post-merge verification so bugs that only appear in production context are caught immediately after merge -- not days later. This closes the "last mile" gap where QA passes locally but production diverges (stale files, unapplied migrations, CSP violations from injected scripts).

Core Features & Use Cases

  • Phase-driven verification: verify PR merge state, CI status on main, production deployment health, and file freshness.
  • Optional browser verification for UI changes, and post-merge reporting/compound updates.

Quick Start

Run this skill after a PR merge to verify the merge, CI results, production health, and post-merge checks.

Frequently Asked Questions about postmerge

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

FAQPage Schema
How do I verify production health after a PR merge?

Post-merge verification automates production health checks by validating main CI results, deployment health, file freshness, and optional browser checks immediately after a PR merge.

Why does production diverge from local QA after a merge?

Production diverges from local QA after a merge due to stale files, unapplied migrations, or CSP violations from injected scripts, which post-merge verification detects by checking file freshness and deployment health.

What does a post-merge verification process include?

A post-merge verification process includes phase-driven checks for PR merge state, CI status on main, production deployment health, file freshness, optional browser verification for UI changes, and post-merge reporting.

Do I need browser checks for post-merge CI verification?

Browser checks for post-merge CI verification are optional and specifically applicable when UI changes exist, ensuring that injected scripts or interface modifications do not cause production issues.

How do I catch production bugs immediately after a merge?

You catch production bugs immediately after a merge by running automated post-merge verification that closes the last mile gap, detecting issues like stale files and unapplied migrations before they escalate.

What is the best way to automate post-merge CI checks on main?

The best way to automate post-merge CI checks on main is using a phase-driven verification skill that validates merge state, CI results, production health, and file freshness in sequence.