praxis

Plugin praxis from marketplace grimoire in Jartan-LLC/grimoire. Commands read from the repo's manifest — 2 days ago.

Skills (21)

• address-review

  Work through review findings on a PR, or on a branch before it has one, one at a time

• api-error-patterns

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

• code-hygiene

  Language-agnostic code hygiene -- no dead/reinvented/duplicated code, truthful names, real implementations, and scoped (never blanket) diagnostic suppressions.

• code-structure

  Language-agnostic structural craft -- decompose on responsibility not size, prefer deep modules over shallow piles, and shape cohesion, coupling, interfaces, error contracts, and data invariants. Sibling to code-hygiene, comment-hygiene and readable-code.

• comment-hygiene

  Comment truthfulness -- what a comment must tell the reader that the code can't, the KEEP/DELETE/EXEMPT/CONDITIONAL taxonomy, tombstone and retold-fact detection, and comment density across a diff. Sibling to code-hygiene, code-structure and readable-code.

• create-issue

  Create a GitHub issue using the appropriate template

• create-pr

  Create a pull request for implemented changes from a GitHub issue

• docs-patterns

  Documentation conventions -- doc types, structure, register, per-type rules, and quality standards.

• frontend-patterns

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

• implement-issue

  Implement a GitHub issue, optionally from an existing plan

• information-placement

  Where each kind of information belongs -- commit message, PR description, code comment, docstring, README, changelog, docs page, issue, or nowhere -- what no text may hold, and how a project's own rules override those defaults.

• logging-patterns

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

• plain-writing

  Plain, accurate prose that informs -- what to keep, what to cut, plain voice, and a final wording pass that removes filler and AI writing patterns.

• plan-issue

  Analyze a GitHub issue and create an implementation plan

• readable-code

  Language-agnostic local-clarity craft -- shape control flow, the naming of a whole set, and reading order so a body reads straight down with the smallest working set. Sibling to code-hygiene, comment-hygiene and code-structure.

• review-cycle

  Take a branch through review rounds until two come back clean, then open its draft PR

• review-pr

  Review a pull request, or a branch before it has one, using specialized reviewer agents

• review-severity

  One severity model for code review -- Critical/Important/Minor by consequence-if-shipped (impact x reachability), with confidence as a separate report gate.

• testing-patterns

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

• voiced-writing

  Writing in a person's or a project's voice for blog posts, essays, site copy and personal writing -- voice from a sample or the kind of text, inventing nothing, keeping what carries the voice, and a final wording pass.

• workspace-patterns

  Where an agent keeps its working files -- plans, research, reviews, notes, state to resume from -- one folder per effort under the main checkout's .claude/workspace/, one subfolder per branch, and where worktrees go.

Subagents (6)

• backend-reviewer

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

• doc-reviewer

  Reviews documentation for conciseness, accuracy, and consistency, and where information sits in the PR title, description and commit messages. Use on every PR.

• frontend-reviewer

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

• general-reviewer

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

• structure-reviewer

  Reviews structural and readability craft -- decomposition, cohesion, coupling, interfaces, data modeling, control flow, and naming. Use after non-trivial code changes.

• test-reviewer

  Reviews test coverage and CI/CD correctness. Use after test or workflow changes.

Hooks (5)

• SessionStart

  node -e "const r = process.env.PLUGIN_ROOT; if (r) require(r + '/hooks/scripts/sync-codex-agents.js')"

• SessionStart

  node -e "const r = process.env.CLAUDE_PLUGIN_ROOT; if (r) require(r + '/hooks/scripts/suggest-skills.js')"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/suggest-skills.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/suggest-compact.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/check-console-log.js"

Similar plugins