Update a changelog

Update the project's existing changelog from repository evidence. Preserve its established format unless the user explicitly requests migration. When the project already follows Keep a Changelog, use the example changelog as the target structure.

Invocation

This skill is model-invoked. Use it automatically after completing work that produces a notable change for users, operators, integrators, or security reviewers in a project with an existing changelog. It can also be invoked manually for release preparation, historical entries, or corrections.

If no changelog exists, ask the user to invoke /create-changelog when it is installed. Otherwise, report that the project needs an initial changelog rather than creating one through this workflow.

Project context

For project work, reuse applicable project instructions and the existing working agreement once per context. Check relevant decision/effect authority, safety, verification/review, documentation and continuation guidance; equivalent layouts are valid. Missing or conflicting common guidance blocks dependent project work: name the gap and recommend explicit setup/reconciliation without starting it or inventing policy. A conditional tracker, model or domain gap blocks only that capability. A skill update does not change project permissions.

Workflow

1. Read the existing convention

Read the complete changelog before editing it. Identify: