Release
This skill should be used when the user asks to "make a release", "create a release", "cut a release", "release a new version", "publish a release", or mentions preparing for release. Provides comprehensive workflow for reviewing changes, updating changelog, determining semver bump, and publishing.
Security Assessment
About Release
The Release skill is designed to streamline and systematize the process of creating and publishing new versions of the linear-cli project. It addresses the common challenges of managing releases, such as ensuring all changes are properly documented, semantic versioning is correctly applied, and the release is executed with appropriate quality checks. By following a structured workflow, this skill reduces the risk of errors, ensures transparency in the changelog, and simplifies collaboration among developers involved in the release process.
This skill offers a comprehensive set of capabilities for managing the release lifecycle. It guides users through reviewing recent commits, adding user-facing changelog entries, and verifying them for accuracy. It provides clear criteria for categorizing changes into Keep a Changelog types and recommends semantic versioning (major, minor, patch) based on the nature of the changes. Once approved by the user, it automates the changelog release, executes quality checks, and ensures proper tagging in the version control system. These features collectively enable consistent, reliable, and auditable release management.
The Release skill is particularly useful for developers, release managers, and teams maintaining the linear-cli project who want a structured approach to releasing software. It is suitable for situations where multiple contributors are making changes, as it ensures that all relevant modifications are captured and properly attributed. Target users benefit from the skill's ability to reduce manual errors, provide clear release guidance, and maintain high-quality software standards while keeping the changelog up-to-date and semantically versioned.
FAQ
When should I use the Release skill?
Use this skill when preparing to publish a new version of linear-cli, ensuring that all changes are documented, tested, and versioned correctly.
What tools do I need to use this skill?
You need the changelog skill for changelog management, svbump for version bumping, jj for version control operations, and just for running release tasks.
How does the skill determine the semantic version bump?
It evaluates changelog entries and recommends a major, minor, or patch bump based on the type of changes, such as breaking changes, new features, or bug fixes.
Can internal or non-user-facing changes be included in the release?
No, the skill focuses on user-facing changes. Internal refactoring, documentation-only updates, and minor CI/build changes are typically excluded from the changelog.
Does this skill handle testing and quality checks?
Yes, it includes running quality checks such as linting, formatting, type checks, and tests before finalizing the release and tagging.
Install Release
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
schpet/linear-cli