Agent skill
review
(ePost) Use when user says "review", "check my code", "is this good", "look at this before I commit", or "suggest improvements" — detects review type (code quality, a11y, or general improvements) and runs the appropriate review
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/review-klara-copilot-epost-agent-kit
Metadata
Additional technical details for this skill
- connections
-
{ "enhances": [] } - argument hint
- [--code | --a11y | --improvements]
SKILL.md
Review — Unified Review Command
Auto-detect and execute the appropriate review workflow.
Step 0 — Flag Override
If $ARGUMENTS starts with --code: load references/code.md and execute.
If $ARGUMENTS starts with --a11y: load references/a11y.md and execute.
If $ARGUMENTS starts with --ui: load references/ui-mode.md and execute. Delegate to epost-muji.
If $ARGUMENTS starts with --improvements: run improvements inline (see below).
Otherwise: continue to Auto-Detection.
Aspect Files
| File | Purpose |
|---|---|
references/code.md |
Ultrathink edge cases, then parallel verify with reviewers |
references/a11y.md |
Review accessibility compliance (WCAG 2.1 AA) |
references/ui-mode.md |
Lightweight UI component review by focus area |
references/improvements.md |
Review auto-improvement metrics, detect patterns |
Auto-Detection
Analyze $ARGUMENTS keywords:
| Keyword match | Load Reference |
|---|---|
| "a11y", "accessibility", "wcag" | references/a11y.md |
| "ui", "component", "token", "klara", "muji" | references/ui-mode.md → epost-muji |
| "improvements", "metrics", "patterns" | Run improvements inline (see below) |
| Default (no keyword match) | references/code.md |
Review-Improvements (Inline)
When dispatching review-improvements, run inline instead of forking (uses haiku model, restricted tools):
-
Read session metrics from
.epost-data/improvements/sessions.jsonl -
Read
.epost-data/improvements/sessions.jsonl -
Present findings grouped by severity (high → medium → low)
-
For each finding: explain detection, recommended action, next step
-
If no findings: report healthy, show session count
-
Summary table: severity × count
Execution
For code and a11y reviews: load the reference file and execute its workflow. For improvements: execute inline per the Review-Improvements section above.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?