Automate feature branch shipping after QA clearance with four git options.
npx skills add https://github.com/davekim917/bootstrap --skill team-ship-davekim917
Please help me install this Agent Skill. Skill: team-ship Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-ship Command: npx skills add https://github.com/davekim917/bootstrap --skill team-ship-davekim917
This Skill streamlines the final shipping step in a feature workflow by validating QA clearance, verifying branch status, and offering explicit shipping options to ensure only safe, intentional changes reach main.
Invoke the /team-ship command on a feature branch that has cleared /team-qa and is ready for shipping.
High-intent search queries and answers about installing and using this skill.
Automated branch shipping validates QA clearance and uncommitted changes before presenting four explicit options: merge locally, push for PR, keep branch, or discard. This enforces prerequisites and verifies test status to ensure safe, intentional changes reach main.
The options for shipping a feature branch once QA is cleared include merging locally, pushing for a PR, keeping the branch, or discarding it. These four explicit choices enforce intentional shipping decisions without modifying code.
A branch lifecycle workflow enforces prerequisites by verifying test status, checking branch state, and ensuring QA clearance is explicitly granted or waived. It blocks shipping if uncommitted changes are detected, ensuring deterministic git workflow execution.
You cannot push a feature branch for a PR if there are uncommitted changes. The workflow requires a clean working directory and verifies branch status before presenting shipping options, preventing accidental or incomplete code from reaching the remote repository.
The best way to finalize a feature release after passing QA without modifying code is to invoke an automated shipping command. It validates QA clearance, checks branch state, and executes a deterministic git workflow with a structured completion summary.
You need a separate QA validation step before automated branch shipping. The workflow checks that QA has explicitly cleared or waived the feature branch, ensuring test status is verified and branch prerequisites are met before any shipping options are presented.
greglambCreate an isolated Git worktree for feature development without disrupting the current workspace.
blakesimsValidate feature branch merge readiness with integration checks and summaries.
zeronx798Scan staged git changes for security issues and quality regressions.
omerakbenAutomate Git branching, CI/CD gates, and Vercel production deployments.
