release

The release skill serves as the comprehensive orchestration engine for managing the software release lifecycle of the Worktrunk project. It is designed for maintainers who need to perform reliable, reproducible releases while ensuring compliance with semver standards and maintaining a high-quality, human-readable changelog. By automating repetitive administrative tasks, it minimizes the risk of human error during the critical phases of versioning and distribution.

• Executes pre-release verification using cargo test and validates API compatibility via cargo-semver-checks to detect breaking changes before publication.

• Automates the version bump process across Cargo.toml, Cargo.lock, and internal documentation, ensuring consistency across the repository.

• Performs intelligent changelog management by auditing git logs, filtering out internal refactors, and identifying user-facing changes to include in the release notes.

• Credits external contributors and issue reporters by cross-referencing commit history and linked pull requests, ensuring the community receives proper acknowledgment.

• Coordinates with GitHub CLI (gh) to streamline the merge-to-main process, tagging release commits, and pushing to triggers for automated CI pipelines.

• Synchronizes internal integrity digests (such as SHA-256 for agent skill documentation) to ensure that downstream consumers and documentation systems remain perfectly aligned with the codebase.

• The skill requires a clean working tree to execute bump operations safely and assumes standard environment tools like cargo, git, and gh are configured correctly.

• Users should review the proposed release type (patch, minor, or major) based on the semver-checks output provided during the execution flow.

• It relies on specific naming conventions for release pull requests and branch management to interact correctly with GitHub Actions workflows.

• For contributors and reporters, the skill provides patterns for linking issues and PRs, ensuring that the final output is well-structured and follows the project's documentation standards.

• This agentic workflow is intended to be used as an end-to-end task; simply request a new version release, and the agent will guide you through the automated steps, from validation to final tag push.