/ship-pr (interactive-pr-shipper)
Customizable end-to-end feature shipping workflow with interactive user preferences, automated issue creation, quality gates, AI PR reviews, and sequential merges.
⚙️ Interactive Configuration & Saved Preferences
When this skill is invoked:
- Check for Saved Config: Look for
.pr_shipper_config.jsonin the workspace root or app data config folder. - Interactive Selection:
- If the user explicitly asks to "edit options" OR if
.pr_shipper_config.jsondoes not exist: Prompt the user usingask_questionwithis_multi_select: trueto pick enabled workflow stages:(Recommended) Issue Creation: Create GitHub Issue and link PR (Closes #issue)(Recommended) AI PR Review: Post self-review checklist comment on PR(Recommended) Stash Backup: Create backup/stash tag before staging files(Recommended) Quality Gates: Run Jest unit tests, ESLint & Playwright E2E(Recommended) Auto-Merge: Sequentially rebase onto main and merge PRs
- If the user explicitly asks to "edit options" OR if
- Persist Settings: Save selected options to
.pr_shipper_config.jsonfor future runs.
🚀 Execution Workflow
Stage 1: Feature Grouping & Stash Backup
- Group uncommitted files by logical feature area.
- If Stash Backup enabled: Run stash backup (
backup/<feature>/<timestamp>).
Stage 2: Quality Gates
- If Quality Gates enabled: Execute Jest, ESLint, and Playwright E2E browser tests.
Stage 3: GitHub Issue Creation & Branch Setup
- If Issue Creation enabled: Call GitHub API to create issue and reference
Closes #<issue_num>in PR description. - Create feature branch
feat/<feature-name>off latestmain.
Stage 4: Pull Request Creation & AI Review
- Build comprehensive PR description (Purpose, File Changes, Blast Radius, Test Results).
- If AI PR Review enabled: Post automated review comment with quality checklist.
Stage 5: Sequential Rebase & Auto-Merge
- If Auto-Merge enabled: Rebase feature branch onto
mainto resolve conflicts and merge PR intomain.