메뉴
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, 版本, 發布, 變更日誌.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | release-standards |
| scope | universal |
| description | 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, 版本, 發布, 變更日誌. |
Language: English | 繁體中文
Version: 1.1.1 Last Updated: 2026-01-30 Applicability: Claude Code Skills
Core Standard: This skill implements Versioning. For comprehensive methodology documentation, refer to the core standard.
This skill provides semantic versioning and changelog formatting standards.
MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]
Examples:
2.3.1
1.0.0-alpha.1
3.2.0-beta.2+20250112
| Component | When to Increment | Example |
|---|---|---|
| MAJOR | Breaking changes | 1.9.5 → 2.0.0 |
| MINOR | New features (backward-compatible) | 2.3.5 → 2.4.0 |
| PATCH | Bug fixes (backward-compatible) | 3.1.2 → 3.1.3 |
| Identifier | Stability | Audience |
|---|---|---|
alpha | Unstable | Internal team |
beta | Mostly stable | Early adopters |
rc | Stable | Beta testers |
| Category | Usage |
|---|---|
| Added | New features |
| Changed | Changes in existing functionality |
| Deprecated | Soon to be removed |
| Removed | Removed features |
| Fixed | Bug fixes |
| Security | Vulnerability fixes |
For complete standards, see:
For AI assistants, use the YAML format file for reduced token usage:
ai/standards/changelog.ai.yaml## [VERSION] - YYYY-MM-DD
### Added
- Add user dashboard with customizable widgets (#123)
### Changed
- **BREAKING**: Change API response format from XML to JSON
### Fixed
- Fix memory leak when processing large files (#456)
### Security
- Fix SQL injection vulnerability (CVE-2025-12345)
Mark breaking changes with BREAKING prefix:
### Changed
- **BREAKING**: Remove deprecated `getUserById()`, use `getUser()` instead
# Create annotated tag (recommended)
git tag -a v1.2.0 -m "Release version 1.2.0"
# Push tag to remote
git push origin v1.2.0
1.0.0-alpha.1 < 1.0.0-alpha.2 < 1.0.0-beta.1 < 1.0.0-rc.1 < 1.0.0
This skill supports project-specific configuration.
CONTRIBUTING.md for "Disabled Skills" section
CONTRIBUTING.md for "Release Standards" sectionIf no configuration found and context is unclear:
CONTRIBUTING.md:## Release Standards
### Versioning
This project uses **Semantic Versioning** (MAJOR.MINOR.PATCH).
### Changelog
This project follows **Keep a Changelog** format.
In project's CONTRIBUTING.md:
## Release Standards
### Versioning
This project uses **Semantic Versioning** (MAJOR.MINOR.PATCH).
### Changelog
This project follows **Keep a Changelog** format.
### Release Process
1. Update version in package.json
2. Update CHANGELOG.md
3. Create git tag with `v` prefix (e.g., v1.2.0)
4. Push tag to trigger release workflow
| Version | Date | Changes |
|---|---|---|
| 1.1.0 | 2026-01-02 | Added: Release Workflow Guide with complete release process |
| 1.0.0 | 2025-12-24 | Added: Standard sections (Purpose, Related Standards, Version History, License) |
This skill is released under CC BY 4.0.
Source: universal-dev-standards
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
審視 ECC（everything-claude-code）分發名單，包含兩個模式： (A) 既有清單瘦身：分析 distribution.yaml.enabled 與本地 skills/ 的重疊性與品質，輸出 enabled_remove 建議； (B) 新項目導入評估：根據 ecc-catalog.yaml 與上次更新範圍，介紹 ECC 上游新增 skill、分析適用情境、建議是否加入 enabled。 Use when: (1) 評估 ECC 分發名單是否該瘦身、(2) ECC 上游新增 skill 後決定要不要導入、 (3) 想為終端使用者產 ecc-profile.yaml starter、(4) 季度 / 半年一次定期審視。 Triggers: "分析 ECC skill", "ECC 重疊", "ECC 清單瘦身", "ECC 新項目", "ECC 上游新增", "要不要導入", "ecc analyze", "ecc new items review", "ecc profile starter", "ECC 品質審視".
用追問把模糊需求壓成專案語言，並在必要時更新 CONTEXT.md 或 ADR。 Use when: 需求還不清楚、術語不一致、要進 OpenSpec 前需要需求對齊、 或使用者想先 stress-test plan 而不是直接實作。
找出架構摩擦與 deep module 候選，但不直接修改實作程式碼。 Use when: 使用者要架構回看、找重構候選、改善可測性、 或把實作中暴露的架構摩擦整理成 OpenSpec 候選。
建立 MP 工作入口層的專案規則。Use when: 首次導入 mattpocock/skills 改寫版、 需要設定 docs/agents/、需要讓 Claude Code 與 Codex 共同讀取 issue tracker、 triage states、domain docs 規則，或 mp-* 技能缺少專案入口脈絡。
將 plan、PRD、OpenSpec change 或對話摘要切成可驗證的垂直切片。 Use when: 需要把大型需求拆成 OpenSpec tasks、GitHub issue draft、 或本地 Markdown 工作項目；不適用於直接 TDD 實作。