release-standards
Semantic versioning and changelog formatting for software releases.Use when: preparing releases, updating version numbers, writing changelogs.Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.
Security Assessment
Detected risks:
About release-standards
The release-standards skill provides a structured approach to software versioning and changelog formatting, following industry-standard practices like Semantic Versioning (SemVer) and the Keep a Changelog format. This skill helps developers maintain consistency when preparing releases, updating version numbers, and documenting changes in a clear and standardized format. By adhering to these standards, teams can ensure that their software releases are easily understood and traceable, which is essential for collaboration and long-term maintainability.
FAQ
What is Semantic Versioning and how does it work?
Semantic Versioning (SemVer) is a versioning system that uses three numbers: MAJOR, MINOR, and PATCH. Each number is incremented based on the type of changes made in the software. MAJOR changes break compatibility, MINOR changes add functionality in a backward-compatible manner, and PATCH updates fix bugs. This skill uses this versioning scheme to ensure releases are predictable and clear.
How does the changelog formatting work?
The changelog format follows the Keep a Changelog guidelines, categorizing changes into sections like Added, Changed, Fixed, and Security. Each section documents the nature of the change, and breaking changes are explicitly marked with a **BREAKING** prefix. This format helps users and developers quickly understand the impact of each release.
Can this skill be used with projects that don't follow Semantic Versioning?
Yes, while this skill is designed with Semantic Versioning in mind, it can still be used for projects that use a different versioning system. However, the default behavior assumes the use of Semantic Versioning and a changelog format consistent with Keep a Changelog.
How do I configure this skill for my project?
Configuration is detected automatically based on the project's `CONTRIBUTING.md` file. If no configuration is found, the skill defaults to Semantic Versioning and Keep a Changelog. You can manually add the configuration to `CONTRIBUTING.md` to specify versioning and changelog formats for your project.
Install release-standards
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
AsiaOstrich/universal-dev-skills