AI Skill Market Insights

Real data. Real impact.

Popularity

Rising

Emerging

Active Users

0+

Developers

Time Saved

2+ hrs

Per week

Quality

4/5

Excellent

Be Part of the 0+ Developer Community

Skills give you superpowers. Install in 30 seconds.

📝 by @davehappyminion

Build Changelog

Generate a formatted changelog from git history since the last tag.

1. Find Last Tag

Using git, find the most recent tag:

Look for semantic version tags (v1.0.0, 1.2.3, etc.)
If no tags exist, use the first commit as the starting point

2. Gather Commits

Get all commits since the last tag:

Exclude merge commits (focus on actual changes)
Include commit hash, message, author, and date

3. Categorize Changes

Group commits by type based on commit message patterns:

4. Build the Changelog

Format the changelog:

# Changelog

## [Unreleased] — YYYY-MM-DD

### Features
- Description of feature ([commit hash])

### Bug Fixes
- Description of fix ([commit hash])

### Improvements
- Description of improvement ([commit hash])

### Other
- Description ([commit hash])

---
**X commits** by Y contributors since LAST_TAG

5. Present and Save

Present the changelog. Offer to:

Save it to
```
CHANGELOG.md
```
in the repo
Copy it to clipboard for a GitHub release
Append to existing changelog

Notes

Link commit hashes if the repo has a remote URL
Combine related commits into single entries where it makes sense
Keep descriptions user-facing — "added dark mode" not "refactored theme provider"
If the repo uses conventional commits, categorization is automatic

License

MIT

Build Changelog

Build Nightly Project

AI Skill Market Insights

Be Part of the 0+ Developer Community

Build Changelog

1. Find Last Tag

2. Gather Commits

3. Categorize Changes

Categories

4. Build the Changelog

5. Present and Save

Notes

License

Quick Start

Install Command

TEAR & SHARE

Tags

Check Dependencies

Clean Docker

Check Repos

Send Expense Report

Channels

Learn

Compare

Company