Skip to content

This release consolidates several plugins into unified packages. The dev plugin now includes documentation, technical writing, git workflows, plan review, and auto-formatting. The tenzir plugin combines TQL and OCSF functionality.

A new emoji reaction-based changelog workflow lets you approve, reject, or modify changelog suggestions directly in PR comments using GitHub reactions.

Git, plan, and formatter plugins merged into dev plugin

Section titled “Git, plan, and formatter plugins merged into dev plugin”

Jan 22, 2026 · @mavam, @claude

The git, plan, and formatter plugins have been consolidated into the dev plugin, creating a comprehensive developer utilities platform. This consolidation removes three separate plugins and unifies their capabilities within the dev plugin.

Git workflows are now part of dev:

  • @dev:committer agent commits changes with automatic cohesion analysis to split orthogonal changes
  • @dev:pr-maker agent creates pull requests on GitHub
  • dev:addressing-pr-comments skill addresses PR review comments
  • dev:writing-commit-messages skill guides cohesive commit messages

Plan review capabilities moved to dev:

  • Plan review hooks (review-plan.sh, notify-plan-review.sh, notify-review-start.sh) now run as part of dev workflows
  • Automated plan evaluation integrates with code review tools
  • Review prompts and notifications are now scoped to the dev plugin

Auto-formatting workflows integrated:

  • format-hook.sh and formatting logic now part of dev plugin
  • Automatic formatting after Write and Edit operations
  • Unified hook configuration for all dev-based operations

The consolidation maintains all existing functionality while providing a more cohesive experience for development workflows. Standalone projects and module-based projects continue to be supported.

Unified dev plugin replaces docs and prose

Section titled “Unified dev plugin replaces docs and prose”

Jan 22, 2026 · @mavam, @claude

The docs and prose plugins have been consolidated into a new dev plugin. Users must update their plugin configuration to replace docs@tenzir and prose@tenzir with dev@tenzir.

The new dev plugin combines documentation workflows with technical writing guidance into a single plugin for developer utilities. The skills are now dev:docs-authoring and dev:technical-writing, and the documentation agent is @dev:docs-updater.

Migration guide:

Update your .claude/settings.json to replace the old plugins with the new one:

"plugins": [
"docs@tenzir",
"prose@tenzir",
"dev@tenzir"
]

Removed commands:

The /docs:write, /docs:review, and /docs:pr commands have been removed. Use @dev:docs-updater instead for autonomous documentation workflows.

Skill mapping:

OldNew
docs:authoringdev:docs-authoring
prose:technical-writingdev:technical-writing

Agent mapping:

OldNew
@docs:writer@dev:docs-updater

Unified tenzir plugin replaces tql and ocsf

Section titled “Unified tenzir plugin replaces tql and ocsf”

Jan 22, 2026 · @mavam, @claude

The tql and ocsf plugins have been consolidated into a new unified tenzir plugin. Users must update their plugin configuration to replace tql@tenzir and ocsf@tenzir with tenzir@tenzir.

The new tenzir plugin combines all TQL and OCSF functionality into a single, cohesive experience with two workflow skills (/tenzir:make-parser and /tenzir:make-ocsf-mapping) and an OCSF subagent (tenzir:ocsf) for schema questions. This simplifies plugin management by reducing the number of plugins needed for Tenzir development workflows.

Migration guide:

Update your .claude/settings.json to replace the old plugins with the new one:

"plugins": [
"tql@tenzir",
"ocsf@tenzir",
"tenzir@tenzir"
]

The docs:reader agent has been removed as it’s superseded by general documentation lookup patterns.

Jan 15, 2026 · @mavam, @claude · #8

Changelog entries are now generated as suggestions in PR comments rather than automatically committed. You can approve, reject, or modify suggestions using GitHub emoji reactions.

React with 👍 to accept and commit the entry, 👎 to reject when no changelog is needed, or 😕 to regenerate with different content. Additional reactions let you adjust the style: 🚀 makes entries more technical, 👀 makes them simpler, and 😄 adds more wit.

The workflow polls reactions every minute and automatically applies your choice. This gives you control over changelog content before it’s committed to your PR.

Updated documentation URLs after ship plugin rename

Section titled “Updated documentation URLs after ship plugin rename”

Jan 15, 2026 · @mavam, @claude

The documentation URLs in the ship and tql plugins now correctly reference ship-framework.md instead of the obsolete changelog-framework.md. This completes the transition from the old changelog plugin name to the new ship plugin name, ensuring all documentation links remain functional.