This major release renames the changelog plugin to ship to better reflect its focus on release engineering. Subagents now require explicit skill declarations in their YAML frontmatter, and tool configurations have been updated to use the consolidated Skill tool.
💥 Breaking Changes
Section titled “💥 Breaking Changes”Changelog plugin renamed to ship
Section titled “Changelog plugin renamed to ship”The changelog plugin has been renamed to ship to better reflect its broader focus on release engineering. Users who have installed the changelog plugin should update their configuration to use ship instead.
🚀 Features
Section titled “🚀 Features”Explicit skill declarations for subagents
Section titled “Explicit skill declarations for subagents”Subagents now explicitly declare required skills in their YAML frontmatter using
the skills: field. This change aligns with Claude Code’s updated behavior
where subagents no longer inherit skills from the parent conversation.
The validation script now verifies that all skill references in agent definitions point to existing skills, catching broken references before deployment.
🔧 Changes
Section titled “🔧 Changes”Updated tool configurations to use Skill instead of SlashCommand
Section titled “Updated tool configurations to use Skill instead of SlashCommand”The SlashCommand tool has been merged into the Skill tool in recent Claude Code versions. This updates tool configurations in the changelog adder GitHub Action and the docs writer agent to reflect this change, removing the redundant SlashCommand reference while keeping Skill.
Changelog-adder action uses tenzir-changelog for PR comments
Section titled “Changelog-adder action uses tenzir-changelog for PR comments”Jan 6, 2026 · @mavam, @claude · #4
The changelog-adder GitHub Action now uses tenzir-changelog to render PR
comments instead of manual frontmatter parsing. This fixes two formatting
issues: a trailing separator when the created field is missing, and
hard-wrapped body text that rendered with explicit line breaks.
The action also supports multiple changelog entries per PR. When a PR adds entries across several plugins, all entries appear in a single comment with proper headings and attribution links.
Initial plugin version set to 0.0.0 for proper first release bumping
Section titled “Initial plugin version set to 0.0.0 for proper first release bumping”The plugin template now specifies 0.0.0 as the initial version, enabling the first release to use standard bump flags (--patch, --minor, --major) to produce typical initial versions like 0.0.1, 0.1.0, or 1.0.0.