Automate committing, pushing, creating a PR, merging, and cleaning up GitHub branches.
npx skills add https://github.com/yves-s/just-ship --skill ship-yves-s
Please help me install this Agent Skill. Skill: ship Source: https://github.com/yves-s/just-ship/tree/main/skills/ship Command: npx skills add https://github.com/yves-s/just-ship --skill ship-yves-s
It removes the need for manual intervention when finishing a development branch, automating the entire sequence from committing changes to merging the pull request on the main branch.
T-123-fix-login can run the skill to ship the changes without any prompts or manual steps.Run /ship on your feature branch to automatically commit, push, open a PR, merge it, and clean up.
High-intent search queries and answers about installing and using this skill.
Automating the commit, push, PR, and merge workflow requires a tool that orchestrates these sequential Git actions end-to-end. This skill executes the entire process autonomously, from committing changes to merging the pull request and cleaning up the branch.
You can automatically update board tickets when creating a pull request by configuring a Board API or legacy Supabase MCP. This skill attaches review and preview URLs to the corresponding tickets during the autonomous merge sequence.
The autonomous pull request workflow requires the GitHub CLI to interact with your GitHub repository. You also need a local Git repository and a development branch named with an embedded ticket number to trigger the automation.
Handling preview deployments and post-merge clean up is automated by stopping dev servers and managing environments like Shopify, Vercel, or Coolify. This skill performs necessary environment clean-up steps immediately after merging the pull request.
The best way to ship a feature branch without manual Git prompts is using an autonomous workflow tool. Running the skill on a branch like T-123-fix-login commits, pushes, opens a PR, merges it, and cleans up in a single run.
You should not use an autonomous Git merge workflow if your development branch lacks an embedded ticket number in its name. The automation also requires explicit configuration for preview deployments and board ticket updates to function correctly.
JuanMS20Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.
s3nex-comCoordinate pull request lifecycle from review through merge with mandatory gates.
bradtaylorsfSynchronizes Linear ticket statuses with Git workflow events via API and gh CLI.
oborchersEnforce git tag-based production deployments with manual approval gates.