promote

Run pre-flight checks and open a production PR after human approval.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Soria-Inc/soria-stack --skill promote-soria-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/Soria-Inc/soria-stack/tree/main/promote
Command: npx skills add https://github.com/Soria-Inc/soria-stack --skill promote-soria-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental or premature pushes to production by enforcing a structured, review-first promotion process that combines environment diffs, verification artifacts, and human approval before opening a production PR.

Core Features & Use Cases

  • Pre-flight checklist: Collects soria env status, soria env diff, git state, verification and dashboard-review artifacts, and dbt test results to present a single promotion summary.
  • Human-gated PR creation: Pushes the branch and opens a GH PR only after explicit human approval, capturing a reproducible promotion artifact.
  • Canary & rollback guidance: Runs or recommends a post-merge canary via dashboard-review and documents the safe rollback flow using soria revert.
  • Use Case: Promote a validated dive and its dbt marts from a preview worktree to prod with confidence and an auditable artifact.

Quick Start

Use /promote to run the pre-flight checks, review the env diff and verification artifacts, and open a PR to promote the current dev branch to production only after you explicitly approve.

Frequently Asked Questions about promote

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

FAQPage Schema
How do I safely promote dbt models from a dev branch to production?

Safe dbt promotion requires collecting environment diffs, dbt test results, and verification artifacts before opening a production PR. This approach prevents premature pushes by running pre-flight checks and gating on explicit human approval.

What is a review-first promotion workflow in CI?

A review-first promotion workflow enforces human approval before pushing code to production by aggregating git state, environment diffs, and dashboard reviews into a single summary. It uses gh to create a PR only after receiving explicit approval.

Can I use git and gh to automate production PR creation with human approval?

Yes, you can automate production PR creation using gh after enforcing explicit human approval. The workflow requires a clean git worktree and pushes the branch to open a GitHub PR only when approval is granted, capturing a reproducible promotion artifact.

Does the promotion process support canary releases and rollback documentation?

The promotion process supports canary releases by running or recommending post-merge dashboard reviews. It documents the safe rollback flow using soria revert, ensuring you can safely revert changes if issues arise during the canary phase.

What prerequisites are needed to run environment diff checks for production promotion?

Running environment diff checks for production promotion requires a clean git worktree and soria CLI outputs. You must also gather verification artifacts and dbt test results to present a complete promotion summary before human-gated PR creation.

When should I not use an automated promotion pipeline?

You should not use an automated promotion pipeline when your git worktree is unclean or dbt tests fail. Promotion requires explicit human approval and successful pre-flight checks, meaning unresolved verification artifacts block the PR creation.