dev

Guide through releasing a project via remote workflow or local tenzir-ship (detect, stage, commit, publish, verify).

Run parallel code review on changes. Use when reviewing a PR, checking code quality, or auditing changes.

Create a changelog entry for PR changes. Use when adding changelog entries, running tenzir-ship, or automating CI workflows.

Commit changes autonomously for automated workflows. Use when staging files, creating commits, or automating git workflows.

Edit Tenzir documentation. Use when writing docs, updating guides, or syncing docs with code without creating a PR.

Fix review findings with commits. Use when addressing findings from /dev:review.

Plan fixes for review findings. Use when creating fix tasks from triaged findings.

Create a pull request on GitHub for current changes. Use when opening a PR, pushing a topic branch, or submitting changes for review.

Review API design, modularity, and complexity. Use when evaluating coupling, SOLID principles, or code organization.

Review documentation quality, accuracy, and completeness. Use when checking docstrings, README accuracy, or API docs.

Extract GitHub PR review comments as findings. Use when processing feedback from human reviewers and bots on pull requests.

Review performance, complexity, and resource efficiency. Use when checking big O complexity, memory usage, or N+1 queries.

Review implementation plans via external models. Use when validating plans before execution.

Review naming quality, idiomatic patterns, and code clarity. Use when checking variable names, code style, or comprehension.

Review input validation, injection risks, and secrets exposure. Use when checking for SQL injection, XSS, command injection, or credential leaks.

Review test coverage, edge cases, and behavioral testing. Use when checking test quality, missing assertions, or test isolation.

Review user experience, clarity, and discoverability. Use when checking error messages, CLI help text, or user feedback.

Triage review findings. Use when filtering false positives, grouping related findings, or deduplicating reviewer overlap.

Address GitHub PR review feedback. Use when responding to reviewers, resolving threads, or handling review comments.

Author documentation for Tenzir projects. Use when creating or updating tutorials, guides, explanations, reference, or integrations.

Edit Tenzir documentation. Use when writing, updating, or validating docs in .docs/.

Review methodology for code changes with confidence scoring. Use when spawning reviewer agents, rating issue severity (P1-P4), or scoring review confidence.

Review methodology for implementation plans. Use when evaluating plan quality, completeness, or risk.

Ship changes through the PR lifecycle. Use when shipping changes, creating draft PRs, adding changelogs before merge, pushing finalized changes, or updating documentation.

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.

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.

2 hooks across 2 events