Create a changelog

Create a human-readable CHANGELOG.md from evidence in the repository. Follow the example changelog.

Invocation

Start only when the user explicitly requests creation of the project's first changelog or invokes create-changelog by name, slash command or the runtime's explicit skill expansion. An expanded invocation counts only when it originates from the user's request. A missing changelog, source mention, quoted or agent-generated command, or another skill's recommendation does not activate this procedure. Without that user request, stop and leave the original task to its existing handler.

If a changelog already exists, use /update-changelog when available rather than replacing it. When it is unavailable, preserve the existing file and report that creation is unnecessary.

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. Establish the history

Inspect the project documentation, package metadata, tags, releases, commit history, merged pull requests, and issue references available locally. Determine: