ptp-deploy

Commits, pushes, merges, and deploys a feature branch through a gated GitHub pipeline.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-deploy-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-deploy
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-deploy
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-deploy-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a finished feature branch involves many error-prone manual steps: writing a commit message, pushing, opening a PR, fixing failing checks, waiting on approvals, merging, triggering a deploy workflow, and recovering from failed deploys. This Skill automates that entire terminal pipeline while respecting branch protection rules and never bypassing required human approvals. ## Core Features & Use Cases - End-to-end ship pipeline: Derives a Conventional Commit message from OpenSpec change artifacts, commits, pushes, creates or reuses a PR, runs a bounded fix loop for conflicts and failing checks, merges with squash, and deletes the branch. - Approval-aware gating: Detects required PR approvals via GitHub reviewDecision, stops with a needs-human-action payload when an approval is unmet, and resumes through a dedicated re-entry command after a collaborator approves. - Deploy and deploy-fix loops: Auto-detects or uses a configured GitHub Actions deploy workflow, watches the run, and fixes failed deploys on dedicated deploy-fix branches merged through the same PR mini-flow, with a merge-only mode that skips deploy entirely. - Use Case: After finishing a reviewed feature branch, run the deploy command to have the branch committed, pushed, PR'd, merged to master, and deployed via GitHub Actions, landing back on a clean base branch. ## Quick Start Run /ptp:deploy from your feature branch to commit, push, merge, and deploy the change to production.

Frequently Asked Questions about ptp-deploy

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

FAQPage Schema
How do I deploy a feature branch to production with GitHub Actions?▼

Run /ptp:deploy from the feature branch. It commits with a derived Conventional Commit message, pushes, creates or reuses a PR, fixes failing checks, squash-merges, dispatches the detected deploy workflow, and returns you to a clean base branch.

How do I merge a PR without running the deploy workflow?▼

Use /ptp:merge-to-master, which runs the same commit, push, PR, fix, and merge pipeline but skips the deploy and deploy-fix phases by design, even when a deploy workflow exists in the repository.

Can the pipeline approve its own pull request on GitHub?▼

No. GitHub blocks PR authors from approving their own PRs, so the skill never runs gh pr review --approve. When branch protection requires an approval, it stops with a needs-human-action payload and resumes via /ptp:deploy-pr-approved after a collaborator approves.

What happens when a deploy workflow run fails after merging?▼

The skill cuts a deploy-fix branch from the updated base branch, diagnoses the failed run log, applies the fix, merges it through the same PR mini-flow, and re-dispatches the deploy. The loop is bounded by maxFixRounds, defaulting to 3.

Why does the deploy command stop on the master or main branch?▼

The skill requires a feature branch because there is nothing to deploy from the base branch. It refuses to run on master or main and instructs you to re-run the command from the feature branch holding the change.

What happens if no deploy workflow exists in the repository?▼

The deploy phase degrades gracefully: it reports that no deploy action was detected, skips the deploy step, and continues to land on a clean base branch without raising an error.