Developer utilities including documentation, changelogs, code review, plan review, git workflows, auto-formatting, and releases. Provides documentation workflows with the Diataxis framework, technical writing guidance based on Google’s style guide, changelog management with tenzir-ship, parallel code review with specialized reviewers and automated fix execution, plan review with external AI tools, git commit/PR workflows, and automatic file formatting after edits.
Features
Section titled “Features”- 📚 Docs Authoring Skill: Guidance on the Diataxis framework, section selection, and Tenzir docs conventions
- ✍️ Technical Writing Skill: Style guidelines for clear technical documentation following Google’s developer documentation style guide
- 📝 Changelog Adder Agent: Creates changelog entries for PR changes, suitable for CI automation
- 🔍 Code Review Command: Spawns specialized reviewers in parallel, triages findings, creates fix tasks, and executes fixes with GitHub thread resolution
- 🚀 Release Command: Guides through releasing a project with tenzir-ship
- 🔄 Finalize Command: Adds changelog entry, commits, and pushes changes
- 🔬 Plan Reviewer Agent: Reviews implementation plans using external AI models (Codex, Gemini, Opus) with structured evaluation methodology
- 📦 Committer Agent: Stages and commits changes with cohesion analysis and automatic splitting of unrelated changes
- 🔀 PR Maker Agent: Creates GitHub pull requests with proper branching and commit workflows
- 🤖 Fixer Agent: Opus-powered agent that fixes findings. In PR mode, commits, pushes, and resolves GitHub threads. In batch mode, applies fixes without individual commits
- 🎯 Triager Agent: Filters low-confidence findings, groups related issues, and deduplicates cross-reviewer overlap for focused review
- 📋 Planner Agent: Creates ordered fix tasks with file-level dependencies to prevent merge conflicts
- 🔧 Auto-Formatting Hook: Automatically formats files after every Write or Edit operation using language-specific formatters
Installation
Section titled “Installation”Use the plugin manager UI in Claude Code.
- Run
/pluginin Claude Code Enter - Go to Marketplaces Tab
- Select + Add Marketplace Enter
- Type
tenzir/claude-pluginsEnter - Install dev from the plugin list
Add the marketplace (once), then install the plugin with your preferred scope.
# Add the Tenzir marketplace (only needed once)claude plugin marketplace add tenzir/claude-plugins
# Install to user scope (default)claude plugin install dev@tenzir
# Install to project scope (shared with team)claude plugin install dev@tenzir --scope project
# Install to local scope (gitignored)claude plugin install dev@tenzir --scope localAdd the marketplace and plugin to your settings file.
{ "extraKnownMarketplaces": { "tenzir": { "source": { "source": "github", "repo": "tenzir/claude-plugins" } } }, "enabledPlugins": { "dev@tenzir": true }}Capabilities
Section titled “Capabilities”| Type | Name | Description |
|---|---|---|
| Skill | addressing-reviews | Address GitHub PR review feedback. Use when responding to reviewers, resolving threads, or handling review comments. |
| Skill | docs-authoring | Author documentation for Tenzir projects. Use when creating or updating tutorials, guides, explanations, reference, or integrations. |
| Skill | reviewing-changes | Review methodology for code changes with confidence scoring. Use when spawning reviewer agents, rating issue severity (P1-P4), or scoring review confidence. |
| Skill | reviewing-plans | Review methodology for implementation plans. Use when evaluating plan quality, completeness, or risk. |
| Skill | technical-writing | Write clear technical documentation following Google’s style guide. Use when writing docs, README files, API documentation, code comments, user guides, or asking about documentation style. |
| Skill | writing-commit-messages | Write git commit messages for Tenzir repositories. Use when committing changes, running git commit, drafting commit messages, detecting staged changes, or asking about commit format and subject lines. |
| Command | /dev:finalize | Add changelog entry, commit, and push. Use when finishing a feature, preparing for merge, or completing PR work. |
| Command | /dev:release | Guide through releasing a project with tenzir-ship (detect, stage, commit, publish, verify). |
| Command | /dev:review | Run parallel code review on changes. Use when reviewing a PR, checking code quality, or auditing changes. |
| Agent | dev:changelog-adder | Create a changelog entry for PR changes. Use when adding changelog entries, running tenzir-ship, or automating CI workflows. |
| Agent | dev:committer | Commit changes autonomously for automated workflows. Use when staging files, creating commits, or automating git workflows. |
| Agent | dev:docs-updater | Update the official Tenzir documentation. Use when documenting code changes, writing guides or tutorials, or syncing docs with code. |
| Agent | dev:fixer | Fix review findings with commits. Use when addressing findings from /dev:review. |
| Agent | dev:planner | Plan fixes for review findings. Use when creating fix tasks from triaged findings. |
| Agent | dev:pr-maker | Create a pull request on GitHub for current changes. Use when opening a PR, pushing a topic branch, or submitting changes for review. |
| Agent | dev:triager | Triage review findings. Use when filtering false positives, grouping related findings, or deduplicating reviewer overlap. |
| Hook | PostToolUse | Triggers on Write, Edit |
Updating documentation
Section titled “Updating documentation”For hands-off documentation, delegate to the docs updater subagent:
Document the latest changes @dev:docs-updaterThe subagent writes docs, reviews them, runs linting, and creates a PR against
tenzir/docs—all without further input.