This major release standardizes skill naming with python:following-conventions and replaces the plugin-specific release command with the generic /changelog:release command. It also adds a dependency upgrade guide for Python projects.
🚀 Features
Section titled “🚀 Features”Add changelog add command to plugin
Section titled “Add changelog add command to plugin”Dec 11, 2025 · @mavam, @claude
Add the /changelog:add command to streamline creating changelog entries. This command provides an interactive workflow guided by the changelog-management skill, reducing the complexity of manual entry creation. Documentation has been reorganized to feature this new command and simplify the skill guidance.
Add releaser subagent to changelog plugin
Section titled “Add releaser subagent to changelog plugin”Add a releaser subagent to the changelog plugin to automate the release workflow using tenzir-changelog. This subagent guides projects through the complete release process, including version determination, release notes generation, and publishing to GitHub.
Add /changelog:release command
Section titled “Add /changelog:release command”The changelog plugin now includes a /changelog:release command that guides
through the release workflow for any project using tenzir-changelog. The
command auto-detects the project type (e.g., Python via pyproject.toml) and
applies language-specific steps like quality gates and version bumping.
🔧 Changes
Section titled “🔧 Changes”Improve releaser agent reliability with Sonnet model and process guardrails
Section titled “Improve releaser agent reliability with Sonnet model and process guardrails”Dec 15, 2025 · @mavam, @claude
Upgrade the releaser agent to use Claude Sonnet instead of Haiku for improved reliability and constraint adherence. Add a “Follow the Process” section that explicitly instructs the agent to use the tenzir-changelog CLI and /changelog:release command rather than bypassing the workflow with direct gh or git tag commands, ensuring consistent and safe release practices.
Improve component awareness in changelog workflow
Section titled “Improve component awareness in changelog workflow”Dec 15, 2025 · @mavam, @claude
The /changelog:add workflow now checks changelog/config.yaml for available
components before creating entries. When a component clearly fits the change,
it should be selected. Cross-cutting changes (e.g., CI work) can still omit
components.
Improve changelog skill discoverability
Section titled “Improve changelog skill discoverability”Rewrite the changelog-management skill description to focus on concrete trigger moments (finishing features, wrapping up commits and PRs) rather than tool-centric language.
Use —co-author for AI-assisted development
Section titled “Use —co-author for AI-assisted development”Use --co-author for AI-assisted development instead of --author. The CLI infers the primary author automatically; --co-author appends to the list while --author overrides it entirely.
Document multi-value flags and human author requirement
Section titled “Document multi-value flags and human author requirement”Dec 5, 2025 · @mavam
The example now shows --author, --component, and --pr passed multiple times. Added note that every entry requires at least one human author.
Use --description-file instead of --description
Section titled “Use --description-file instead of --description”Dec 5, 2025 · @mavam
The --description-file flag reads the description from a file, avoiding shell escaping issues that can occur with inline --description arguments.
Add Markdown formatting best practice
Section titled “Add Markdown formatting best practice”Dec 5, 2025 · @mavam
The skill now advises to use backticks for code and technical terms, and to use emphasis and bold where it improves clarity.
🐞 Bug Fixes
Section titled “🐞 Bug Fixes”Fix release command documentation
Section titled “Fix release command documentation”Dec 9, 2025 · @mavam
Updated the /changelog:release command documentation to use release notes instead of the deprecated release show command, matching the current tenzir-changelog API.
Clarify entry type selection criteria in changelog skill
Section titled “Clarify entry type selection criteria in changelog skill”The skill now provides clearer guidance on when to use bugfix vs change entry types, reducing misclassification.
Clarify publish step to use release notes for preview
Section titled “Clarify publish step to use release notes for preview”The /changelog:release command now recommends using ‘release notes’ to preview before publishing instead of running ‘release publish’ without —yes.
Always pass —description to skip interactive editor
Section titled “Always pass —description to skip interactive editor”Dec 5, 2025 · @mavam
The skill now instructs Claude to always pass --description when
adding entries to avoid launching an interactive editor.