skills.rest
dus2183-commits
dus2183-commitsCOMMUNITY
Explore all skills by this author →
GitHub

flutter-changelog

Generate Keep a Changelog formatted CHANGELOG.md from git history and conventional commits.

Updated Apr 10, 2026
Search Tags:#automation#git#changelog#release-notes#conventional-commits#keep-a-changelog
One-click install
npx skills add https://github.com/dus2183-commits/flutter-skills --skill flutter-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flutter-changelog
Source: https://github.com/dus2183-commits/flutter-skills/tree/main/flutter-changelog
Command: npx skills add https://github.com/dus2183-commits/flutter-skills --skill flutter-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of CHANGELOG.md by converting git logs into a Keep a Changelog format using Conventional Commits, enabling teams to publish consistent release notes with minimal manual effort.

Core Features & Use Cases

  • Automatic changelog generation: parse git history to produce a structured Keep a Changelog document that reflects the current release.
  • Conventional commits mapping: classify commits by prefixes (feat, fix, docs, refactor, perf, BREAKING CHANGE) into Added, Fixed, Documentation, Changed, and Breaking Changes.
  • Workflow integration: suitable for release pipelines and developer workflows to generate release notes for each version and support audits.

Quick Start

Tell Claude to generate a changelog for version 1.2.0.

Frequently Asked Questions about flutter-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Keep a Changelog formatted changelog from git history?▼

Conventional commits map directly to Keep a Changelog categories: feat prefixes become Added, fix becomes Fixed, docs map to Documentation, and BREAKING CHANGE flags populate the Breaking Changes section, ensuring structured release notes.

What's the best way to automate release notes generation for a new version?▼

Automating release notes generation is handled by parsing git logs through conventional commit prefixes, producing a structured CHANGELOG.md that reflects the current release with minimal manual effort across your development pipelines.

Do I need conventional commits to use this changelog generator?▼

The skill fits seamlessly into release pipelines and developer workflows, generating release notes for each version and supporting audits. You can trigger it by asking Claude to generate a changelog for a specific version like 1.2.0.

Can I integrate automated changelog generation into my release workflow?▼

The skill fits seamlessly into release pipelines and developer workflows, generating release notes for each version and supporting audits. You can trigger it by asking Claude to generate a changelog for a specific version like 1.2.0.

How does a conventional commit changelog generator categorize different commit types?▼

A conventional commit changelog generator categorizes commit types by mapping prefixes: feat becomes Added, fix maps to Fixed, docs to Documentation, refactor and perf to Changed, while BREAKING CHANGE flags populate the Breaking Changes section.

Related Skills

Explore More Software Engineering Skills→
aaron-vazaaron-vaz
1

conventional-commits

Validate Git commit messages against the Conventional Commits specification.

Community
Intermediate
PlagueHOPlagueHO
4

release-changelog

Update CHANGELOG.md and create a release tag from commits since the last version tag.

Community
Advanced
Greenmamba29Greenmamba29

changelog-generator

Generate structured CHANGELOG.md entries from git commit history and semantic versioning tags.

Community
Intermediate
monaccodemonaccode
30

changelog-automation

Generate change logs from Git commit messages in Keep a Changelog format.

Official
Intermediate