Automate merges, tests, version bumps, changelog updates, and PR creation.
npx skills add https://github.com/shhubbh/flowstate --skill ship-shhubbh
Please help me install this Agent Skill. Skill: ship Source: https://github.com/shhubbh/flowstate/tree/main/.claude/skills/gstack/ship Command: npx skills add https://github.com/shhubbh/flowstate --skill ship-shhubbh
Ship workflows require manual, error-prone steps to move code from feature branches to production. This Skill automates detect + merge base branch, run tests, review diff, bump version, update CHANGELOG, commit, push, and create a PR, reducing human toil and bottlenecks.
Initiate a ship command to automatically package, test, and publish your changes with a PR.
High-intent search queries and answers about installing and using this skill.
Automating a Git workflow to merge base branches and create pull requests requires a remote repository with base branch tracking. The process merges the base branch locally, runs tests, bumps versions, updates the CHANGELOG, and opens a PR via GitHub or GitLab APIs.
Automated version bumping and CHANGELOG updates work by modifying VERSION files and changelog entries during the release flow. The automation commits these changes locally before pushing, ensuring versioning metadata stays synchronized with daily commits and hotfixes.
Yes, you need GitHub or GitLab API access to automate end-to-end code shipping. The workflow requires tooling to create PRs via these APIs, along with a Git workflow that supports base branch tracking and a remote repository to push commits.
The best way to run tests automatically before merging feature branches to main is to detect and merge the base branch locally first. This ensures local testing against the latest state before bumping versions and opening a pull request.
Yes, you can use automated release flows for hotfixes across multiple Git branches. The automation applies to teams who want a hands-off release flow for daily commits, hotfixes, or feature deployments, managing merges and PRs end-to-end.
You should not use an automated pull request creation workflow if your repository lacks a Git workflow with base branch tracking or remote repository access. The automation requires tooling to modify VERSION and CHANGELOG files and create PRs via GitHub or GitLab APIs.
imbue-aiMerge parent branch commits into child branches in a git stack.
GenEducationMerge a pull request, wait for CI and deployment, and verify production health with canary checks.
JovieIncMerge base into feature branch, run tests, and create a pull request.
jm199seoAutomate Git release shipping by merging base branch, testing, updating CHANGELOG, bumping VERSION, and creating a PR.
