commit-with-changelog-first

Generate changelogs before running tests, commits, and syncs.

Updated Mar 27, 2026

Search Tags:#automation #git #changelog #commit #qa #ci #release-workflow

Ready to run

npx skills add https://github.com/jangtrinh/EaseUI-Agent --skill commit-with-changelog-first

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-with-changelog-first
Source: https://github.com/jangtrinh/EaseUI-Agent/tree/main/.claude/skills/commit-with-changelog-first
Command: npx skills add https://github.com/jangtrinh/EaseUI-Agent --skill commit-with-changelog-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release workflow by ensuring a changelog is generated before any commit, unifying changelog discipline with code changes and release readiness.

Core Features & Use Cases

Changelog-first release orchestration: enforce that changelogs are generated before commits.
End-to-end release steps: run tests, stage changes, commit with conventional format, perform ByteRover/PM Hub sync, and push.
Branch safety and governance: prevents direct commits to main/master and ensures feature branches are used unless explicitly requested.

Quick Start

Execute the end-to-end release workflow by generating the changelog first, then running tests, staging changes, and pushing to the feature branch.

Frequently Asked Questions about commit-with-changelog-first

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

FAQPage Schema

How do I automate changelog generation before making a git commit?▼

You can automate changelog-first commits by enforcing a strict sequence that generates changelog entries before staging, testing, and committing code changes. This workflow unifies changelog discipline with release readiness to prevent undocumented pushes.

What is a changelog-first release workflow and when do I need it?▼

A changelog-first release workflow ensures changelogs are generated before any code commit, unifying changelog discipline with code changes. You need it for software projects requiring disciplined commit history and synchronized changelog updates across CI workflows.

How do I prevent direct commits to main while automating a release workflow?▼

You can prevent direct commits to main by applying branch safety checks that block pushes to main/master and enforce feature branch usage unless explicitly requested. This governance step is built into the automated release sequence.

Can I run tests and sync to PM Hub as part of an automated commit workflow?▼

Yes, you can run tests and perform PM Hub sync as part of an end-to-end release workflow. After generating the changelog, the sequence runs tests, stages changes, commits with conventional format, syncs, and pushes to the feature branch.

Does this automated commit workflow enforce conventional commit formatting?▼

Yes, the automated commit workflow enforces conventional commit formatting during the staging and commit phase. This ensures disciplined commit history is maintained automatically alongside the synchronized changelog updates.

Why should changelog updates happen before running tests and committing code?▼

Changelog updates should happen before commits to unify changelog discipline with release readiness, ensuring documentation reflects intended changes before code is finalized. This prevents risky pushes by validating tests against the documented release context.