deploy

Create a deploy branch and PR from a feature branch to a target environment.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/takemi-ohama/ai-plugins --skill deploy-takemi-ohama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/deploy
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill deploy-takemi-ohama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating environment deploys for a feature branch can be error-prone and time-consuming. This skill automates the end-to-end workflow by generating a deploy branch from your feature branch (named <feature>to<env>) and opening a PR to the target environment branch after integrating with main.

Core Features & Use Cases

  • Automates deploying all feature changes by merging origin/main and creating a deploy branch named {feature}to{env} and a PR to the environment branch.
  • Prevents duplicate PRs by checking for an existing deploy PR on the same branch.
  • Supports common workflows to qa/staging and release environments with automated main synchronization.

Quick Start

Run /ndf:deploy <env-branch> to create a deploy PR from your current feature branch to the specified environment after syncing with main.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate creating a deployment PR from a feature branch to a staging environment?

You can automate a deployment PR by running a single command to generate a deploy branch from your feature branch and open a PR to the target environment. The workflow syncs with main first to ensure all changes are integrated before deployment.

What is the best way to prevent partial-commit deployments when merging feature branches?

Preventing partial-commit deployments is handled by automatically merging origin/main into your feature branch before creating the deploy branch. This ensures the target environment receives a fully synchronized set of feature changes.

Can I push changes directly from the main branch to a qa environment?

No, the deployment workflow explicitly blocks deployments from the default branch. You must initiate the process from a dedicated feature branch to ensure proper branch management and avoid deploying directly from main.

How does this deployment automation handle existing pull requests for the same feature branch?

This deployment automation handles existing pull requests by checking for an active deploy PR on the same branch. It prevents duplicate PRs from being created, ensuring a single deployment pipeline for your feature changes.

What happens if there are merge conflicts when syncing with main before a deployment?

When merge conflicts occur during the main synchronization step, the deployment workflow handles them gracefully. This prevents broken deployments and allows you to resolve conflicts without losing your feature branch state.