katana-openapi-client

Write comprehensive tests using project conventions: AAA pattern, edge-case checklist, httpx.MockTransport, conftest fixtures, parametrize where it reads better than copy-paste.

Audit Prefab UI card builders (`build_*_ui` in `katana_mcp_server/src/katana_mcp/tools/prefab_ui.py`) for user-centric content: real names over IDs, no redundant text dumps, named helpers over ad-hoc rendering. Reports findings; does not modify code. Use when reviewing card UX or after touching `prefab_ui.py`.

Groom the Rolling Backlog (project #5) by reading current state and proposing diffs — not re-deriving the queue from scratch. Surfaces drift between issue state and project status, missing classification, and stale priorities. Asks per-category confirmation before mutating the board.

Quick pre-flight validation of staged and unstaged changes before committing. Lighter than the verifier/code-reviewer agents — focuses on catching common mistakes in the current changeset.

Scan editable code for tech debt, anti-patterns, and improvement opportunities across 5 categories. Reports findings; the code-modernizer agent applies fixes.

Open a PR for the current feature branch — self-review the diff, organize commits, push, create the PR, wait for CI and review, then address feedback. Use when implementation is complete and ready for review.

Address PR review comments — fetch all unresolved comments, fix the issues, validate with `uv run poe check`, commit, push, and reply to each comment on GitHub. Use when asked to handle PR review feedback.

Resolve a shipped-order discrepancy — customer received different items than Katana recorded. Pull the customer-facing record, locate the linked Katana SO/MO, decide whether a BOM-driven split is needed (when an assembled good shipped as its component parts), then apply correct_manufacturing_order + correct_sales_order with operator-judgment gates between phases. Verify against the source of truth at the end.

Generate or update docstrings, ADRs, README sections, cookbook recipes, or user guides following Katana's documentation standards.

Six-dimension code review of the current branch's diff against main. Delegates to the code-reviewer agent for the actual review and reports findings.

Skeptically validate that implementation is complete and works. Heavier than the verifier agent — exercises the feature, checks integration, and confirms regression protection.