publish

Publish Rust crates to crates.io with pre-flight validation and version management.

19|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/zmerlynn/manifold-csg --skill publish-zmerlynn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/zmerlynn/manifold-csg/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/zmerlynn/manifold-csg --skill publish-zmerlynn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish crates to crates.io with pre-flight checks to ensure a clean, validated release process and prevent broken publishes.

Core Features & Use Cases

  • Pre-flight validation: verify a clean working tree, run builds and tests, and ensure dependencies are in a publishable state.
  • Versioning workflow: coordinate workspace version bumps across multiple crates and enforce workspace integrity during release.
  • Dry-run and release hygiene: support --dry-run, check changelogs/documentation prerequisites, and enforce release discipline.

Quick Start

Run the publish skill to validate and release all four crates in dependency order.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I publish crates to crates.io with pre-flight checks?

Publishing crates to crates.io with pre-flight checks requires validating a clean working tree, running builds and tests, and verifying dependency states. This process ensures a clean, validated release and prevents broken publishes.

How do I coordinate workspace version bumps for multiple Rust crates?

Coordinating workspace version bumps for multiple Rust crates requires enforcing workspace integrity during release. This ensures proper versioning across dependencies, coordinating checks and builds across multiple crates in dependency order.

Can I do a dry-run before publishing crates to crates.io?

Yes, you can perform a dry-run before publishing crates to crates.io. Dry-run support allows you to check changelogs and documentation prerequisites, enforcing release hygiene without making the package live on the registry.

Why does my crate publish fail CI due to chore checks?

Your crate publish fails CI due to chore checks because pre-flight validation enforces release discipline. The process deterministically verifies chore checks per publish guidelines, ensuring all prerequisites are met before releasing.

What is the best way to automate Rust crate releases in CI with deterministic verification?

The best way to automate Rust crate releases in CI with deterministic verification is using a pre-flight workflow that checks for a clean working tree, successful builds and tests, and proper version bumps. This prevents broken publishes by validating state first.