Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.
npx skills add https://github.com/taloncjones/dotfiles --skill ship-taloncjones
Please help me install this Agent Skill. Skill: ship Source: https://github.com/taloncjones/dotfiles/tree/main/claude/skills/ship Command: npx skills add https://github.com/taloncjones/dotfiles --skill ship-taloncjones
Manages the process of transitioning a code branch or pull request from initial implementation to merged state, ensuring all steps including code review, testing, version bump, and cleanup are efficiently handled.
Use the /ship command followed by the PR number or URL to initiate the merge process for the specified pull request.
High-intent search queries and answers about installing and using this skill.
Automating the branch to merge workflow requires validating code review, local and CI testing, version bumping, and post-merge cleanup. You can trigger this entire sequence automatically by invoking the ship command with a specific pull request number or URL.
To ensure pull requests pass co-review before merging, you need an automated gate that invokes the co-review process and verifies all approved changes are fixed. This guarantees only reviewed and validated code transitions to the merged state.
Yes, automated merge workflows can handle post-merge cleanup by automatically executing branch and worktree deletion. This cleanup is triggered immediately after the merge confirmation gate is passed and the pull request is successfully merged.
Adding a merge confirmation gate for human approval in a CI/CD pipeline provides a manual checkpoint after automated testing and version bumping. This gate ensures a human reviews the validated state before the final merge and subsequent automated cleanup tasks are executed.
You can automatically update Jira status as part of your branch merge process by integrating it into post-merge cleanup automation. After the merge confirmation gate is passed, the workflow executes branch deletion alongside the Jira status update.
Yes, continuous integration checks are required to automate your pull request merge process. The workflow ensures the test suite passes locally and validates that the pull request has successful CI checks before proceeding to version bumping and merge confirmation.
HomericIntelligenceCheck GitHub pull request CI/CD status and workflow runs via gh CLI.
kdlbsDelete local git branches marked [gone] and their associated worktrees.
rajveersingh11Automate pull request triage with CI status, review comments, and merge readiness.
jeremy-newhousePromote a dev branch to main after CI health and divergence checks.
