Ship
Ship orchestrates the full release cycle for RTK projects: quality verification, semantic versioning, changelog generation, git tagging, and remote push to activate CI/CD pipelines. Follow pre-release checklists, execute the multi-step workflow, and verify post-release artifacts automatically.
Ship automates your complete release workflow—version bumps, changelog updates, git tags, and CI/CD triggers in one command.
AI-generated summary based on this skill's SKILL.md
Install
rtk-ai/rtk/ship · repository language: Rust
git clone https://github.com/rtk-ai/rtk
cp -r rtk/.claude/skills/ship ~/.claude/skills/shipFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I release a new version with Ship?
Ship orchestrates the complete release cycle for RTK projects. It handles quality verification, semantic versioning decisions, changelog generation, git tagging, and pushing changes to trigger CI/CD pipelines. Follow Ship's pre-release checklists, execute the multi-step workflow, and the tool verifies post-release artifacts automatically.
How does Ship automate build, commit, push workflow?
Ship automates the build, commit, and push workflow by integrating verification steps, version bumping, and git operations into a single orchestrated process. It runs tests and pre-release checks, updates version numbers and changelogs, creates git tags, and pushes all changes remotely to activate your GitHub Actions workflows.
What does Ship do for semantic versioning automation?
Ship manages semantic versioning automation by determining when to bump major, minor, or patch versions based on your release requirements. The tool handles version number updates, maintains changelog entries, and ensures consistent versioning across your RTK project before tagging and publishing.
Can Ship verify build quality before release?
Yes, Ship verifies build quality as part of its pre-release checks. It runs tests, performs build verification, and executes pre-release quality checks before allowing the release to proceed. This ensures your code meets standards before version bumps, tagging, and CI/CD pipeline activation.
Does Ship support release rollback if issues arise?
Ship includes rollback capabilities for critical post-deployment issues. If problems are discovered after release, Ship can yank or rollback releases to maintain project stability and allow you to address issues before re-releasing.
How does Ship trigger GitHub Actions on git push?
Ship commits, tags, and pushes changes to your remote repository, which automatically triggers GitHub Actions workflows configured in your project. This CI/CD integration activates your automated deployment pipeline as part of Ship's complete release orchestration.
SKILL.md
rendered from the published skill — quoted content, verbatim
Ship Release
Systematic release workflow for RTK: build verification, version bump, changelog update, git tag, and push to trigger CI/CD.
When to Use
- Manual invocation: When ready to release a new version
- After feature completion: Before tagging and publishing
- Before version bump: To automate the release checklist
Pre-Release Checklist (Auto-Verified)
Before running /ship, verify:
1. Quality Checks Pass
cargo fmt --all --check # Code formatted
cargo clippy --all-targets # Zero warnings
cargo test --all # All tests pass
2. Performance Benchmarks Pass
hyperfine 'target/release/rtk git status' --warmup 3
# Should show <10ms mean time
/usr/bin/time -l target/release/rtk git status
# Should show <5MB maximum resident set size
3. Integration Tests Pass
cargo install --path . --force # Install locally
cargo test --ignored # Run integration tests
4. Git Clean State
```bash git status # Should show "nothing to commit, working
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/ship/SKILL.md