release-check

Validate pre-release checklist items for software publishing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/paxtone-studio/openkodo --skill release-check-paxtone-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-check
Source: https://github.com/paxtone-studio/openkodo/tree/main/plugins/kodo/skills/release-check
Command: npx skills add https://github.com/paxtone-studio/openkodo --skill release-check-paxtone-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cargo-fmt, cargo-clippy, cargo-test, cargo-audit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents costly release errors by systematically validating all critical pre-release checklist items before publishing a new version.

Core Features & Use Cases

  • Version Consistency Check: Ensures version numbers match across Cargo.toml, plugin manifests, and documentation.
  • Code Quality Gates: Verifies code formatting, linting, test execution, and security audits.
  • Git State Validation: Confirms a clean working directory and synchronization with the remote repository.
  • Documentation Audit: Checks for updated changelogs and version references.
  • Build Verification: Ensures the release binary builds correctly and runs as expected.

Quick Start

Run the release-check skill to validate all pre-release requirements before publishing.

Frequently Asked Questions about release-check

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

FAQPage Schema
How do I validate version consistency across Cargo.toml and plugin manifests before publishing?

Pre-release checklist validation verifies code formatting, linting, test execution, and security audits to ensure code quality gates pass before initiating a release process.

How do I check Git state and documentation completeness before a release?

Pre-release checklist validation verifies code formatting, linting, test execution, and security audits to ensure code quality gates pass before initiating a release process.

What pre-release validation steps should I run to ensure my Rust build is ready for publishing?

Pre-release checklist validation verifies code formatting, linting, test execution, and security audits to ensure code quality gates pass before initiating a release process.

Can I use cargo-audit and cargo-clippy in my CI/CD release checklist?

Pre-release checklist validation verifies code formatting, linting, test execution, and security audits to ensure code quality gates pass before initiating a release process.

Why does my release process fail due to mismatched version numbers in Cargo.toml?

Pre-release checklist validation verifies code formatting, linting, test execution, and security audits to ensure code quality gates pass before initiating a release process.