ai-promote

Promote a staging branch to production by creating an automerge PR.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/svange/augint-shell --skill ai-promote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-promote
Source: https://github.com/svange/augint-shell/tree/main/.agents/skills/ai-promote
Command: npx skills add https://github.com/svange/augint-shell --skill ai-promote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes the configured staging branch to production by creating an automerge PR. Use when dev/staging is ready for release, or saying 'release to production'.

Core Features & Use Cases

  • Automerge PRs to promote builds from staging to production.
  • Provide a report detailing source/target branches, commits included, PR link, automerge state, and blockers that must be resolved before release.
  • Fallback guidance when the promotion command is unavailable.

Quick Start

Run the promotion workflow to promote staging to production via an automerge PR.

Frequently Asked Questions about ai-promote

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

FAQPage Schema
How do I automate promoting a staging branch to production via a pull request?

Automating staging to production promotion is done by creating an automerge pull request. The workflow reports source and target branches, included commits, automerge state, and any blockers that must be resolved before the release proceeds.

What details are reported when merging dev or staging to a production branch?

When merging dev or staging to a production branch, the workflow provides a report detailing source and target branches, included commits, the pull request link, automerge state, and any release blockers requiring resolution.

Can I use this to release from dev to production, or only staging to production?

You can use this workflow for both dev-to-production and staging-to-production release scenarios. It creates an automerge PR to safely promote your configured source branch into the target production branch.

What happens if the branch promotion tool is unavailable during a release?

If the branch promotion tool is unavailable, the workflow provides clear fallback instructions and avoids proceeding with the release. It requires explicit user confirmation before continuing any promotion without the primary tool.

How does automerge handle blockers before a production release?

Automerge identifies and reports any blockers that must be resolved before the production release. It details these issues alongside the PR link and automerge state, preventing the merge until all blockers are cleared.

When should I use an automerge PR instead of manually merging staging to production?

Use an automerge PR when dev or staging is ready for release and you need a tracked, reportable promotion process. It provides commit visibility and blocker detection, which manual merging lacks.