📜 Changelog Automation Skill

​

Purpose

​

Core Philosophy: Focus on User & Developer Impact

• Group Changes by Audience Impact:
  • Added: New features or capabilities.
  • Changed: Modifications in existing functionality.
  • Deprecated: Soon-to-be removed features.
  • Removed: Now-removed features.
  • Fixed: Bug fixes.
  • Security: Vulnerability resolutions.
• Highlight Breaking Changes: Explicitly state migration steps required for developers or users when breaking changes occur.

​

Tooling & Setup Integration

• Conventional Commits: Enforce commit message formatting (feat:, fix:, docs:, refactor:, perf:).
• Automation Tools: Use tools such as @commitlint, standard-version, release-it, or semantic-release.

​

Keep a Changelog Template Format

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Added
- Feature description detailing user benefit ([#123](https://github.com/org/repo/issues/123)).

### Fixed
- Resolved edge case causing transient timeouts during high load.

## [1.0.0] - 2026-09-02

### Added
- Initial stable release of the component.