name	changelog
description	Draft a new version section in CHANGELOG.md for prayer-times by summarising commits since the last release tag. Use when the user says "update the changelog", "prep the changelog for release", "add changelog entry", or anything similar. Draft-only — does not run cargo release.

Update CHANGELOG.md

This project's release flow is: edit CHANGELOG.md (under ## [Unreleased]), then run cargo release <level> --execute (see release.toml and the README's Release process section). release.toml has a pre-release-replacements rule that rewrites ## [Unreleased] into ## [Unreleased] + a new ## [{{version}}] - {{date}} heading as part of the release commit, so the versioned heading and date are injected by cargo-release — this skill never writes them directly. This skill owns drafting the bullets under ## [Unreleased].

Format rules

Follow Keep a Changelog — the existing file already uses it. Do not invent new conventions.
Do not write a ## [X.Y.Z] - YYYY-MM-DD heading yourself. cargo-release inserts it via pre-release-replacements at release time.
Subsection headings, in this order when present: ### Added, ### Changed, ### Deprecated, ### Removed, ### Fixed, ### Security. Omit any that have no entries.
Bullets are short, user-facing, imperative-past ("Added timezone support", "Fixed Julian day calculation"). Group related commits into a single bullet rather than mirroring git history 1:1.
Flag breaking changes explicitly with a leading Breaking: inside the ### Changed or ### Removed bullet — that's the convention used by the 0.4.0 entry.

Steps

Read the current CHANGELOG.md to confirm format and find the most recent released version (the first ## [X.Y.Z] section below ## [Unreleased], if any). Note any bullets already accumulated under ## [Unreleased] — you may be adding to them, not starting fresh.
Find the last release tag with git describe --tags --abbrev=0 (tags are vX.Y.Z). Fall back to the version detected in step 1 if the tag lookup fails.
Survey commits since the last tag with git log <last-tag>..HEAD --no-merges --pretty=format:'%h %s'. Read the commit bodies for any commit whose subject is unclear (git show <sha>).
Ask the user for the target version if it's ambiguous. Suggest one based on the commits: patch for fixes/chores, minor for new features, major for breaking changes. State your reasoning in one sentence and propose X.Y.Z. The version itself isn't written into the changelog (cargo-release injects it), but you still need it to recommend the right cargo release <level> command at the end.
Draft the bullets in memory, grouping commits under the right Keep a Changelog subheadings. Drop purely internal noise (dependency bumps with no user impact, CI-only changes) unless the user has asked for a thorough log.
Insert the bullets under ## [Unreleased] in CHANGELOG.md, merging with any existing bullets already there. Do not add a dated/versioned heading — leave ## [Unreleased] as the only heading above your bullets.
Do not commit, do not bump Cargo.toml, do not run cargo release. Those are the user's next step. End by telling the user the target version you recommended and suggesting the exact cargo release command (e.g. cargo release patch --execute or cargo release 0.4.1 --execute). Remind them that cargo-release will produce a single commit containing both the Cargo.toml version bump and the ## [X.Y.Z] - <date> heading insertion into CHANGELOG.md.

What to skip

Do not rewrite or reorder old released sections.
Do not touch Cargo.toml's version field — cargo-release owns that.
Do not write the versioned ## [X.Y.Z] - YYYY-MM-DD heading — pre-release-replacements in release.toml owns that.
Do not invent changes that aren't in the commit log. If the commits are too terse to summarise faithfully, say so and ask the user to clarify rather than making things up.

Update CHANGELOG.md

Format rules

Follow Keep a Changelog — the existing file already uses it. Do not invent new conventions.

Do not write a ## [X.Y.Z] - YYYY-MM-DD heading yourself. cargo-release inserts it via pre-release-replacements at release time.

Subsection headings, in this order when present: ### Added, ### Changed, ### Deprecated, ### Removed, ### Fixed, ### Security. Omit any that have no entries.

Bullets are short, user-facing, imperative-past ("Added timezone support", "Fixed Julian day calculation"). Group related commits into a single bullet rather than mirroring git history 1:1.

Flag breaking changes explicitly with a leading Breaking: inside the ### Changed or ### Removed bullet — that's the convention used by the 0.4.0 entry.

Steps

Read the current CHANGELOG.md to confirm format and find the most recent released version (the first ## [X.Y.Z] section below ## [Unreleased], if any). Note any bullets already accumulated under ## [Unreleased] — you may be adding to them, not starting fresh.

Find the last release tag with git describe --tags --abbrev=0 (tags are vX.Y.Z). Fall back to the version detected in step 1 if the tag lookup fails.

Survey commits since the last tag with git log <last-tag>..HEAD --no-merges --pretty=format:'%h %s'. Read the commit bodies for any commit whose subject is unclear (git show <sha>).

Ask the user for the target version if it's ambiguous. Suggest one based on the commits: patch for fixes/chores, minor for new features, major for breaking changes. State your reasoning in one sentence and propose X.Y.Z. The version itself isn't written into the changelog (cargo-release injects it), but you still need it to recommend the right cargo release <level> command at the end.

Draft the bullets in memory, grouping commits under the right Keep a Changelog subheadings. Drop purely internal noise (dependency bumps with no user impact, CI-only changes) unless the user has asked for a thorough log.

Insert the bullets under ## [Unreleased] in CHANGELOG.md, merging with any existing bullets already there. Do not add a dated/versioned heading — leave ## [Unreleased] as the only heading above your bullets.

Do not commit, do not bump Cargo.toml, do not run cargo release. Those are the user's next step. End by telling the user the target version you recommended and suggesting the exact cargo release command (e.g. cargo release patch --execute or cargo release 0.4.1 --execute). Remind them that cargo-release will produce a single commit containing both the Cargo.toml version bump and the ## [X.Y.Z] - <date> heading insertion into CHANGELOG.md.

What to skip

Do not rewrite or reorder old released sections.

Do not touch Cargo.toml's version field — cargo-release owns that.

Do not write the versioned ## [X.Y.Z] - YYYY-MM-DD heading — pre-release-replacements in release.toml owns that.

Do not invent changes that aren't in the commit log. If the commits are too terse to summarise faithfully, say so and ask the user to clarify rather than making things up.