praxis

Review a pull request using specialized reviewer agents

Work through review findings on a PR one at a time

Create a GitHub issue using the appropriate template

Create a pull request for implemented changes from a GitHub issue

Implement a GitHub issue, optionally from an existing plan

Reviews backend code for patterns, async correctness, and security. Use after backend code changes.

Reviews documentation for conciseness, accuracy, and consistency. Use after doc changes.

Reviews frontend code for design system compliance, accessibility, and responsive patterns. Use after frontend code changes.

Reviews code for general quality, naming, organization, cleanup, and project standards. Use after any code changes.

Analyzes GitHub issues and designs implementation approaches with alternatives considered, producing actionable plans.

API error response format — machine-readable codes, human-readable reasons, status code rules.

Documentation writing conventions — style, structure, tone, and quality standards.

CSS design system principles — token usage, semantic layering, mobile-first, component isolation.

Logging conventions — level usage, formatting style, structured output.

Integration test philosophy — test observable behavior, fixture composition, canary markers for library internals.

6 hooks across 4 events