changelog

name	changelog
description	Manage changelog entries — add, edit, validate, or summarize changes in main/log.yaml. USE WHEN the user wants to manage changelog entries, add release notes, or validate changelog data.
argument-hint	[action] [description]
model	sonnet

Changelog

Manage structured changelog entries for the Panfactum stack's main (unreleased) channel.

When Invoked

1. Read references: Load the changelog format conventions: @./reference/changelog-format.md

2. Gather context: Run ./scripts/list-changes.ts to see current entries in main/log.yaml.

3. Determine intent: Analyze the user's request against trigger words in the Workflow Routing table below.

4. Select workflow: Choose the appropriate action:

   1. Does the user want to add or edit changelog entries? → UpdateEntry
   2. Does the user want to validate the changelog? → ValidateChangelog
   3. Does the user want to generate a release summary? → GenerateSummary
   4. Does the user want to generate upgrade instructions? → GenerateUpgradeInstructions
   5. Does the user want to condense or merge related entries? → CondenseEntries
   6. Does the user want to enhance, improve, or polish a single entry? → EnhanceEntry
   7. Does the user want to list current changes? → Run ./scripts/list-changes.ts directly
   8. Does the user want to list change IDs? → Run ./scripts/list-change-ids.ts directly
   9. Does the user want to show a specific change by ID? → Run ./scripts/show-change.ts <id> directly
   10. Does the user want to update a specific change by ID? → Run ./scripts/update-change.ts <id> field=value directly
   11. When in doubt: Ask the user which action they want

5. Execute workflow: Report "Running using the changelog skill..." Read and follow the selected workflow completely.

6. Report results: Summarize what was accomplished and suggest next steps.

Workflow Routing

Workflow	Trigger Words	When to Use
UpdateEntry	"add", "new", "log", "record", "entry", "edit", "update", "modify", "reorganize", "fix"	Developer wants to add or edit change entries
ValidateChangelog	"validate", "check", "verify", "review"	Developer wants to check changelog completeness and correctness
GenerateSummary	"summarize", "summary", "highlights", "release", "compile"	Preparing a release — generate summary and highlights from changes
GenerateUpgradeInstructions	"upgrade", "instructions", "migration"	Developer wants to generate or update upgrade instructions from breaking changes
CondenseEntries	"condense", "merge", "collapse", "consolidate", "deduplicate", "reduce"	Developer wants to merge related or redundant entries into consolidated ones
EnhanceEntry	"enhance", "improve", "polish", "quality", "flesh out", "expand"	Developer wants to deeply improve a single entry's quality using source context and external research

Reference

• Changelog Format — log.yaml schema reference, valid enums, structure, and examples
• Upgrade Instruction Format — upgrade.mdx conventions, single-command principle, section guidelines, and examples
• CLI Tools — Available CLI scripts for listing changes and components