Automate the end-to-end ship workflow for code changes.
npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill ship-aimasteracc
Please help me install this Agent Skill. Skill: ship Source: https://github.com/aimasteracc/tree-sitter-analyzer/tree/main/.claude/skills/ship Command: npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill ship-aimasteracc
Ship workflows involve coordinating testing, versioning, changelog updates, commits, and PR creation. This Skill automates the entire process, reducing manual toil and human error.
Trigger the ship workflow on a feature branch to automatically validate, bump versions, update CHANGELOG, commit, push, and open a PR.
High-intent search queries and answers about installing and using this skill.
You can automate your pull request workflow by triggering an automated ship process that runs pre-flight checks, merges the base branch, executes tests, increments versions, updates the CHANGELOG, and opens a PR. This eliminates manual toil across testing, versioning, and PR creation.
An end-to-end ship workflow coordinates validation, versioning, changelog updates, commits, and pull request creation into a single automated process. It ensures consistent validation across testing and governance while reducing human error during code deployment.
Yes, the ship workflow automatically merges the base branch and bootstraps test execution as part of its pre-flight checks. This ensures your feature branch is validated against the latest base before proceeding to version bumping and PR creation.
The best way to ensure consistent versioning is to automate version increments and CHANGELOG updates directly within your ship workflow. This enforces standardized version bumps and changelog entries for every code change pushed to a PR.
Yes, the automated ship process records telemetry for governance and project alignment throughout the workflow. This provides visibility into your automated testing, versioning, and pull request creation steps for compliance purposes.
You should avoid fully automated ship workflows if your code changes require manual intervention for complex merge conflict resolution, custom versioning schemes outside standard bumps, or specialized testing environments not supported by automated pre-flight checks.
timsvoiceSquash commits and create a pull request via gh for code review.
korchasaAutomate final pull request review and merge in an SDLC pipeline.
faionfaionAutomates development workflows with Puppeteer, Playwright, GitHub Actions, Turborepo, pnpm, k6, and Locust.
TioSavichMerge base branch, run tests, bump version, update changelog, commit, push, and create a pull request.
