Stats
Actions
Tags
From autoreview
Use when the agent has a concrete file path (about to edit `src/api/users.ts`) and needs the rules that apply to THAT path. Also use with no path to list all rule ids — triggers "what rules does this project have", "list all rules", "which rules exist", "show me the rules". Other triggers: "before I edit X, what rules apply?", a path reference without a review request. Skip when the agent wants an actual verdict (use autoreview:review); skip when no path yet and the user asks an abstract convention question (use autoreview:guide); skip when no `.autoreview/` exists — use autoreview:setup first.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autoreview:contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Cross-platform.** Snippets below use bash-style env-var syntax (`${CLAUDE_PLUGIN_ROOT}`). Claude Code's Bash tool runs Git Bash on Windows so these work as-is; on native PowerShell substitute `$env:CLAUDE_PLUGIN_ROOT`, on cmd use `%CLAUDE_PLUGIN_ROOT%`. Plugin requires Node ≥22 — only assumed binary.
Cross-platform. Snippets below use bash-style env-var syntax (
${CLAUDE_PLUGIN_ROOT}). Claude Code's Bash tool runs Git Bash on Windows so these work as-is; on native PowerShell substitute$env:CLAUDE_PLUGIN_ROOT, on cmd use%CLAUDE_PLUGIN_ROOT%. Plugin requires Node ≥22 — only assumed binary.
Pre-write use: invoke BEFORE editing a file the first time in a session. Zero LLM cost.
node ${CLAUDE_PLUGIN_ROOT}/scripts/bin/context.mjs <path>
Output is a Markdown list of matching rules with read: <absolute-rule-path> pointers per rule. Open every pointer with the Read tool and internalize the convention before writing — the rule body is the source of truth for the agent's behavior, not the trigger (the trigger only decides applicability).
Skip only when no rules exist in the repo or the path is in an excluded directory.
If you need rules by free-text intent instead of by path, use autoreview:guide skill (text similarity search) — it filters by relevance, not by trigger.
Output shows effective frontmatter — remote rules have any remote_rules[].overrides entries already merged in.
- corp/audit-log-on-handlers [manual]
tier: trivial severity: warning type: manual read: /path/to/rule.md
- corp/no-todo-without-ticket
tier: standard severity: error read: /path/to/rule.md
- corp/legacy-perf-rule [invalid: tier 'bogus' unknown] [manual]
tier: bogus severity: error type: manual read: /path/to/rule.md
Markers:
[manual] — rule has type: manual; it only runs when explicitly invoked with --rule <id>. The pre-commit hook and default autoreview:review skip it silently.[invalid: <reason>] — rule has a frontmatter value error (unknown tier, unknown severity, etc.). The reviewer emits an [error] verdict for every file it matches rather than dispatching to the tier. Fix the rule or its override.If the user wants to see everything defined ("what rules exist?", "show me the rules", "what rules does this project have?"), invoke with no path:
node ${CLAUDE_PLUGIN_ROOT}/scripts/bin/context.mjs
Output lists every rule id + its effective frontmatter summary.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub krzysztofdudek/autoreview --plugin autoreview