dsh-changelog

🚀 Usage

/unreleased                        # preview release candidates since the latest tag
/release-notes 1.2.3               # write release notes for 1.2.3 (release-notes/1.2.3.md)
/release-notes 1.2.0..1.2.3        # write release notes for a range
/setup-release-notes-style [notes] # create or refine .dsh/release-notes-style.md

• /unreleased and /release-notes require an authenticated GitHub CLI (gh auth login)
• /release-notes creates or overwrites its output files; keep .dsh/tmp/ ignored and unpublished

Port notes (vs upstream @noice-tech/pi-changelog@1.3.0)

Kept verbatim: the three prompt files (prompts/release-notes.md, setup-release-notes-style.md, unreleased.md). unreleased.md is byte-identical to upstream (verify with cmp); the other two change only path references — Pi's state-dir convention .pi/ becomes dsh's .dsh/ (e.g. .dsh/tmp/pi-changelog/release-notes-sources/ and .dsh/release-notes-style.md). You can verify this yourself — THIRD_PARTY_NOTICES.md pins the upstream tarball's integrity / shasum and the byte-identical files' SHA-256, with copy-paste comparison commands.

Adapter (new, no upstream counterpart): Cordis namespace entry; the three prompts are registered as slash commands on the commands service; invoking a command delivers the prompt text ($ARGUMENTS substituted with your input) to the agent via agent.followup. /commit and /commit-config belong to the upstream's bundled dependency @noice-tech/pi-commit (a separate package) and are out of scope for this port.

Known limitation: the prompts the agent receives are in English — that is upstream text, kept verbatim and untranslated.