git-changelog

dreamworks2050's avatarfrom dreamworks2050

Generate changelog from git commits and manage versions.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025
[CI and CD]

When & Why to Use This Skill

This Claude skill automates the generation of structured changelogs from Git commit history and streamlines version management. It helps developers maintain clear project timelines, categorize updates into features and fixes, and ensure consistent semantic versioning across software releases.

Use Cases

  • Automated Release Documentation: Quickly generate professional markdown changelogs for new software versions by analyzing and grouping recent commit logs.
  • Version Control Management: Streamline the process of updating version constants in source code and creating Git tags following Semantic Versioning (SemVer) standards.
  • Project Progress Tracking: Summarize development activities over specific timeframes or between tags to keep stakeholders and users informed of technical changes.
  • Standardizing Release Workflows: Grouping raw Git logs into readable categories like 'Added', 'Changed', and 'Fixed' to ensure high-quality, consistent documentation.
namegit-changelog
descriptionGenerate changelog from git commits and manage versions.

Git Changelog Generator

Instructions

When releasing a new version:

  1. Generate commit log: git log --oneline --since="..."
  2. Group by type: Features, Fixes, Changes
  3. Format for changelog: Keep, markdown format
  4. Update version constant: Update PLUGIN_VERSION
  5. Tag the release: git tag v0.1.0

Changelog Pattern

## 0.1.0 - 2025-12-29

### Added

-   Initial release with retro login page
-   Custom login page styling
-   Login redirect functionality

### Changed

-   Updated Howdy boilerplate structure

### Fixed

-   Security: ABSPATH check added to all files

Generate Log Command

# Since last tag
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || v0.0.0)..HEAD

# Since specific date
git log --oneline --since="2025-12-01"

# All commits
git log --oneline -20

Version Update

Update in retrologin.php:

const PLUGIN_VERSION = '0.1.0';

Git Tag

# Create tag
git tag -a v0.1.0 -m "Version 0.1.0"

# Push tag
git push origin v0.1.0

# List tags
git tag -l

Guidelines

  • Follow Semantic Versioning (MAJOR.MINOR.PATCH)
  • Keep changelog in readme.txt or CHANGELOG.md
  • Tag before publishing to WordPress.org
  • Test after version bump