changelog-update

Syncs CHANGELOG.md unreleased section with commits merged since the last update.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill changelog-update-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-update
Source: https://github.com/nseng-ai/ns/tree/main/skills/internal/repository-operations/changelog-update
Command: npx skills add https://github.com/nseng-ai/ns --skill changelog-update-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a changelog current requires manually reviewing every merged commit, deciding which changes are user-visible, and writing consistent entries — a tedious process that teams often skip, leaving changelogs stale or inaccurate. ## Core Features & Use Cases - Incremental Sync: Tracks an "As of" commit marker in the Unreleased section so only new commits since the last sync are processed, with fallback to release tags. - User-Visibility Filtering: Categorizes commits into Major Changes, Added, Changed, Fixed, and Removed while filtering out internal-only work like tests, CI, docs, and refactors. - Approval-Gated Updates: Presents a categorized proposal with roll-up detection and low-confidence flags, and only edits CHANGELOG.md after explicit user approval. - Use Case: After merging a dozen PRs during a sprint, run the skill to get a proposed set of Keep a Changelog-formatted entries, adjust categorizations, and commit an updated changelog in minutes. ## Quick Start Ask the agent to update the changelog with commits since the last release and review the proposed entries before approving.

Frequently Asked Questions about changelog-update

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

FAQPage Schema
How do I update a changelog from git commits automatically?

Run the changelog-update skill, which reads the "As of" marker in your CHANGELOG.md, fetches commits since that point with git log --first-parent, categorizes them, and proposes entries for your approval before editing the file.

How to generate changelog entries that follow Keep a Changelog format?

The skill follows Keep a Changelog 1.1.0 with categories ordered as Major Changes, Added, Changed, Fixed, and Removed. Unreleased entries include the short commit hash in parentheses, and only categories with entries are written.

Does changelog generation work if my repo has no CHANGELOG.md yet?

Yes. When no CHANGELOG.md exists, the skill initializes one from a standard template with an empty Unreleased section and an "As of" marker set to the current HEAD commit, then stops since there is nothing to categorize.

Which commits get excluded from changelog entries?

Commits that are not user-visible are filtered out: test-only, docs-only, CI/CD, build tooling, agent configuration, dependency bumps, merge commits, vague messages like "WIP", and internal refactors with no behavior change.

What happens if the changelog sync marker commit no longer exists?

If the base commit was rewritten by a rebase or squash, the skill falls back to resolving the last release version tag as the base commit, or asks you to provide a starting point manually.