Worktrunk Release Manager FAQs

Question 1

Does this skill handle GitHub Actions monitoring?

Accepted Answer

Yes, it uses the GitHub CLI to watch the release workflow execution status, ensuring that binaries are built and published correctly before finalizing the process.

Question 2

How does the changelog verification work?

Accepted Answer

The skill spawns a specialized subagent that reads the actual file diffs for every commit, ensuring that release notes accurately reflect code changes rather than just relying on potentially misleading commit messages.

Question 3

Can I choose the release type (patch, minor, or major)?

Accepted Answer

Yes. The skill analyzes your changes, provides a recommendation based on project guidelines, and requires your explicit confirmation before proceeding with the version bump.

Question 4

What happens if a release build fails after tagging?

Accepted Answer

The skill includes built-in troubleshooting procedures to safely delete the failed remote and local tags, allowing you to fix the issue and re-release without version conflicts.

Question 5

Is this skill restricted to Rust projects?

Accepted Answer

While it features specific integrations for Cargo and crates.io, the core logic for commit analysis, changelog verification, and Git tag management is applicable to most software projects.

Worktrunk Release Manager

Key Features

Use Cases

Worktrunk Release Manager

Key Features

Use Cases