g-promote-dev

Create a pull request from feature branches to dev with pre-deploy gates.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill g-promote-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: g-promote-dev
Source: https://github.com/withpiper/pipekit/tree/main/skills/g-promote-dev
Command: npx skills add https://github.com/withpiper/pipekit --skill g-promote-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates promoting a feature branch to the integration/dev environment by creating a pull request, running pre-deploy gates, and handling optional migrations across environments.

Core Features & Use Cases

  • PR creation workflow: reads project config, validates working tree, and creates a PR from feature/* to dev with proper titles and bodies.
  • Pre-deploy gate enforcement: executes the configured gate commands to prevent broken promotions.
  • Migration handling: detects new migrations and conditionally applies them to shared or per-environment databases according to config.
  • Linear integration: extracts issue references from branch/commits and transitions linked issues to In Progress, with PR references attached.
  • Use Case: When you finish a feature on a feature/* branch, use this skill to publish to dev for testing with a single command.

Quick Start

Promote the current feature branch to dev by creating a PR after passing the pre-deploy gate.

Frequently Asked Questions about g-promote-dev

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

FAQPage Schema
How do I automate promoting a feature branch to dev via a pull request?

You can automate promoting a feature branch to dev by running a skill that validates your working tree, creates a pull request from feature/* to dev, and executes configured pre-deploy gates. It requires a parseable method.config.md to drive the workflow.

How does database migration handling work when promoting a branch to an integration environment?

Migration handling during branch promotion detects new migrations and conditionally applies them to shared or per-environment databases. The specific deployment strategy is driven by rules defined within your project's method.config.md file.

Can I link Linear issues to pull requests automatically during dev branch promotions?

Yes, Linear integration extracts issue references from your branch name and commits during promotion. It transitions linked Linear issues to In Progress and attaches the pull request reference automatically.

Do I need the gh CLI to create pull requests for feature branch promotions?

Yes, you need the gh CLI installed and authenticated to create pull requests from feature/* branches to dev. A valid Linear MCP connection is also required to enable automatic issue tracking and status transitions.

What are the limitations when using automated gates for dev environment promotions?

Automated gate enforcement only applies to feature/* and fix/* branches. Promotions will fail if pre-deploy gate commands defined in method.config.md do not pass, or if the working tree contains uncommitted changes.

What is the best way to transition Linear tickets when publishing a fix branch to dev?

The best way to transition Linear tickets is using an automated promotion workflow that parses issue references from your fix/* branch, creates the pull request to dev, and updates the ticket status to In Progress with the PR link attached.