Quality

Plannotator Review runs Plannotator's browser-based code review UI against the current worktree or a pull request URL, then returns feedback to address in the same conversation. Use it to get code review annotations and approvals while working in Claude Code.

Plannotator Review opens Plannotator's browser-based code review UI for the current worktree or a pull request URL and acts on any feedback returned.

Review Renovate reviews Renovate bot pull requests that update GitHub Actions dependencies, verifying pinned commit SHAs against upstream tags, checking changelogs for breaking changes, and confirming CI/CD workflow compatibility before merge.

Update Dependencies audits and updates npm/Bun dependencies after verifying maintainers, publish age, provenance, tarball diffs, and changelogs. It bumps safe packages, defers risky ones, and logs audit findings.

Chinese Code Review provides communication templates and priority labels (must-fix/suggest/for-reference) for giving code review feedback in Chinese teams, avoiding over-politeness or bluntness. Use when explicitly invoked via /chinese-code-review to conduct or guide a code review.

Chinese Commit Conventions adapts Conventional Commits for Chinese teams with type tables, commit message templates, breaking change rules, issue linking, and changelog generation configs. Use it to set up commitlint, husky, and commitizen for Chinese-language commit workflows.

Receiving Code Review provides a disciplined process for evaluating code review feedback before acting, verifying suggestions against the codebase, asking clarifying questions when items are unclear, and pushing back with technical reasons when appropriate.

Requesting Code Review dispatches a code review subagent to find issues before they spread. Use it after completing tasks, implementing features, or before merging to validate work against requirements.

Systematic Debugging guides a rigorous four-phase process to find root causes before attempting fixes. Use it for test failures, production bugs, performance issues, or any unexpected behavior.

Test-Driven Development enforces a test-first workflow: write a failing test, see it fail, then write the minimum code to pass before refactoring. Use it for new features, bug fixes, refactors, and behavior changes; no production code without a failing test.

Verification Before Completion enforces running verification commands and checking output before claiming tests pass, builds succeed, or bugs are fixed. It prevents false success claims by requiring evidence for every assertion.

Browser QA reproduces and isolates failures in an embedded browser using an evidence-first loop, then reports whether the failure is locator, timing, session state, or product behavior. Use it for reproducible browser validation, regression checking, or debugging workflows.