skills.rest
FlorianBruniaux
FlorianBruniauxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Automate Rust release workflows with build verification, conventional commits, and remote pushes.

88|6|Updated Feb 2, 2026
Search Tags:#automation#git#workflow#ci/cd#conventional commits#release
One-click install
npx skills add https://github.com/FlorianBruniaux/ccboard --skill ship-florianbruniaux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/FlorianBruniaux/ccboard/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/FlorianBruniaux/ccboard --skill ship-florianbruniaux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the entire release cycle for your project, from building and testing to committing, version bumping, and pushing your code.

Core Features & Use Cases

  • Build Verification: Ensures your code compiles, passes linting, and all tests are green before proceeding.
  • Automated Committing: Creates conventional commit messages based on your changes.
  • Version Bumping: Optionally updates the version in Cargo.toml and commits the change.
  • Push to Remote: Pushes your changes to the configured remote repository.
  • Use Case: Streamline your development process by having a single command that handles all the necessary steps to get your new feature or fix released.

Quick Start

Run the ship skill to build, commit, and push your current changes.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate my Rust release workflow with conventional commits?▼

You can automate your Rust release workflow by running a single command that builds, tests, generates conventional commit messages, bumps versions, and pushes your code to a remote repository.

Can I automatically bump the version in Cargo.toml during a release?▼

Yes, you can automatically bump the version in Cargo.toml during a release. The workflow optionally updates the version in Cargo.toml and commits the change directly to your repository.

Does automated committing support different conventional commit types?▼

Automated committing supports conventional commit message generation for feature, fix, refactor, docs, and chore types. It stages your changes and creates the appropriate commit message based on the modifications.

What is checked during build verification before pushing code?▼

Build verification ensures your code compiles, passes linting, and all tests are green before proceeding. This prevents broken code from being committed or pushed to your remote repository.

Do I need a configured remote repository to automate pushing my changes?▼

Yes, you need a configured remote repository to push your changes. The workflow pushes your committed changes to the configured remote repository as the final step in the release cycle.

Related Skills

Explore More Software Engineering Skills→
luigiinredluigiinred
1

sync-dotfiles

Synchronize Cursor configuration files with a chezmoi-managed dotfiles repository.

Community
Intermediate
robotijnrobotijn
3

changelog-generator

Generate Keep a Changelog 1.1 compliant changelogs from Conventional Commits.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced