Git workflows for Tenzir repositories. Provides commands for committing with well-formatted messages, creating pull requests, and addressing review comments systematically.
Features
Section titled “Features”- 📝 Commit Command: Stage and commit changes with cohesion analysis to split orthogonal changes
- 🔀 PR Command: Create GitHub pull requests with proper descriptions
- 💬 Address PR Comments: Work through review comments with commits and thread resolution
- 🤖 Committer Subagent: Lightweight agent (Haiku) that handles the commit workflow autonomously
- 📖 Writing Commit Messages Skill: Guides commit message format and style when committing
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 git from the plugin list
Run the CLI command with your preferred scope.
# Install to user scope (default)claude plugin install git@tenzir
# Install to project scope (shared with team)claude plugin install git@tenzir --scope project
# Install to local scope (gitignored)claude plugin install git@tenzir --scope localAdd the marketplace and plugin to your settings file.
{ "extraKnownMarketplaces": { "tenzir": { "source": { "source": "github", "repo": "tenzir/claude-plugins" } } }, "enabledPlugins": { "git@tenzir": true }}Capabilities
Section titled “Capabilities”| Type | Name | Description |
|---|---|---|
| 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 | /git:address-pr-comments | Address GitHub PR review comments with commits |
| Command | /git:commit | Commit changes with project-specific workflows |
| Command | /git:pr | Create a pull request on GitHub for current changes |
| Agent | git:committer | Commit staged changes following project conventions. Use when the user wants to commit or asks to save their work to git. |
Committing changes
Section titled “Committing changes”Use /git:commit after making changes:
> /git:commitDetected 2 orthogonal changes in staged files:1. Add user validation to signup form2. Fix typo in error messagesWhich would you like to commit first? [1/2]For hands-off commits, delegate to the @git:committer subagent. It runs on
Haiku and makes decisions autonomously—splitting orthogonal changes and creating
separate commits without prompting:
> @git:committer commit my changesCreating 2 commits...✓ Add user validation to signup form✓ Fix typo in error messagesUse the command when you want control over commit grouping. Use the subagent when you trust it to split and commit everything correctly.