Automate base branch merging, tests, version bumps, changelogs, and pull requests.
npx skills add https://github.com/robertzengcn/aiFetchly --skill ship-robertzengcn
Please help me install this Agent Skill. Skill: ship Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/ship Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill ship-robertzengcn
Manually managing the code shipping workflow—including merging base branches, running tests, updating versions and changelogs, and creating pull requests—is time-consuming and prone to human error, especially for teams with frequent releases.
Use the ship skill to prepare your current feature branch for merging into main, run all required project tests, update the project version and changelog, and open a pull request with all changes ready for review.
High-intent search queries and answers about installing and using this skill.
Automate git pull request creation and version bumping by running a single workflow that merges base branches, executes tests, updates changelogs, and opens pull requests. This eliminates manual steps for code shipping and ensures consistent release processes.
Preparing a feature branch for merging into main requires detecting the base branch, running tests, bumping versions, updating the changelog, and creating a pull request. The workflow enforces pre-merge validation and change documentation before code is merged.
No specific CI-CD platform dependencies are required to use this code shipping workflow. It operates independently without external dependencies, handling merge automation, test execution, and pull request creation directly.
The best way to ensure consistent changelog updates before a merge is to automate the documentation step within the shipping workflow. The process automatically updates the changelog and bumps the project version before creating a pull request for review.
Yes, you can use this to automate merge requests after finishing a bug fix. The workflow proactively suggests running when code is ready to deploy, ensuring all pre-merge checks and change documentation are completed before merging into the main branch.
Teams should automate end-to-end code shipping because manual git commands for merging, testing, and version tracking are time-consuming and prone to human error. Automation enforces pre-merge validation and consistent release processes for frequent deployments.
psyche911Automates Git release workflows from merge to PR creation.
oxieAutomate staging deployment with auto-merge for merged pull requests.
ybbms777Identifies test quality gaps and false confidence risks in code diffs.
tapanshahParse conventional commits to generate changelogs and assess release readiness.
