dev-ship

Merge approved pull requests into develop and update issue boards.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-ship
Source: https://github.com/learnzdevelopmenthub/paadhai/tree/main/.claude/skills/dev-ship
Command: npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill keeps approved feature work from stalling by combining merge approvals, issue board updates, and branch cleanup so develop always reflects the latest completed work without manual coordination.

Core Features & Use Cases

  • Automated Merge Flow: Validates CI status, waits for explicit approval, and performs a squash merge into the develop branch, ensuring consistent history and cleanup of remote feature branches.
  • Project Board Synchronization: Uses GraphQL to move the associated issue to the Done column, keeping stakeholders aligned without requiring manual board edits.
  • Milestone Awareness: Reports open vs closed issues for the current milestone so you know whether to start another feature or trigger the release pipeline.

Quick Start

Invoke dev-ship once your feature PR is approved so it can merge, update the project board to Done, and delete the branch in one run.

Frequently Asked Questions about dev-ship

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

FAQPage Schema
How do I automatically merge a pull request into the develop branch and delete the feature branch?

To automatically merge a pull request, the dev-ship skill performs a squash merge into the develop branch and deletes the remote feature branch after validating CI safety and approval status.

Does merging a pull request require a passing CI state before squashing?

Yes, merging a pull request requires a passing CI state. The process validates CI status and waits for explicit approval before squashing the approved pull request into the develop branch.

Can I update the GitHub project board to Done automatically when a pull request merges?

Yes, you can update the GitHub project board to Done automatically. The merge flow uses GraphQL to move the associated issue to the Done column, synchronizing stakeholders without manual edits.

What is the best way to check milestone progress before starting a new feature?

Checking milestone progress is handled by milestone awareness, which reports open versus closed issues for the current milestone so you know whether to start another feature or trigger the release pipeline.

Do I need GitHub CLI access to automate pull request merges and branch cleanup?

Yes, you need GitHub CLI access to automate pull request merges. The workflow also requires paadhai configuration for project board fields to successfully update issue statuses and delete branches.

Why does pull request branch cleanup fail when the project board configuration is missing?

Pull request branch cleanup and board synchronization fail because the workflow requires paadhai configuration for project board fields to map issues and update statuses correctly during the merge.