release-promotion

Promotes a validated develop branch to main via merge-commit PR after checks.

Updated Aug 23, 2026

Search Tags:#git #release #governance #delta #promotion #ci #merge-commit

Ready to run

npx skills add https://github.com/irvinesunday/Hali --skill release-promotion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-promotion
Source: https://github.com/irvinesunday/Hali/tree/main/.claude/skills/release-promotion
Command: npx skills add https://github.com/irvinesunday/Hali --skill release-promotion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely promoting a validated batch of work from develop to main while preserving release hygiene, comprehensive delta visibility, and explicit operator authorization for merge commits.

Core Features & Use Cases

Pre-flight delta inspection and history reconciliation to identify what landed in develop.
Enforced CI green checks and explicit operator approval prior to promotion.
Promotion PR creation using merge-commit only, with a structured release notes delta and required pre-reads.
Post-promotion verification, auditing, and traceability for release governance.

Quick Start

Run the /release-promotion command with an explicit operator instruction to promote develop to main.

Frequently Asked Questions about release-promotion

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

FAQPage Schema

How do I safely promote a develop branch to main with release governance?▼

Promote develop to main by enforcing pre-flight delta inspection, requiring CI green checks, explicit operator authorization, and merge-commit PR creation to ensure release hygiene and traceability.

What is a merge-commit promotion PR and when do I need it for release cycles?▼

A merge-commit promotion PR safely advances code from develop to main during milestone boundaries. It requires explicit operator authorization, pre-read documentation, and an accurate delta inventory before creation.

How to ensure CI green checks pass before a git branch promotion?▼

Git branch promotion requires enforced CI green checks and explicit operator approval prior to execution. You must complete pre-flight delta inspection and history reconciliation to validate the batch before promotion.

Does this release promotion workflow require pre-read documentation and delta inventory?▼

Yes, release promotion requires pre-read documentation and an accurate delta inventory. It applies during milestone boundaries when operator authorization is explicit and CI validation is green to ensure auditable governance.

How do I audit a git merge-commit promotion after it lands on main?▼

Post-promotion verification and auditing ensure safe git merge-commit traceability. You verify the release governance state by checking the structured release notes delta and validating the promoted batch on main.

Best way to identify what landed in develop before promoting to main?▼

Pre-flight delta inspection and history reconciliation identify what landed in develop before promoting to main. This provides comprehensive delta visibility required for safe merge-commit PR discipline and release governance.