audit

Category: Tools & Productivity | Uploader: Klara-copilot | Downloads: 0 | Version: v1.0（Latest）
(ePost) Audit workflow — auto-detects UI component, a11y, or code audit
Changelog: Source: GitHub https://github.com/Klara-copilot/epost_agent_kit
Directory Structure

Current level: .claude/skills/audit/
📁 references/
- 📄 a11y.md 3.4 KB
- 📄 android-audit-mode.md 2.7 KB
- 📄 audit-report-schema.md 6.3 KB
- 📄 checklist-web.md 2.5 KB
- 📄 close-a11y.md 1.0 KB
- 📄 close-ui.md 1.4 KB
- 📄 delegation-templates.md 5.4 KB
- 📄 ios-audit-mode.md 3.3 KB
- 📄 output-contract.md 6.5 KB
- 📄 report-template.md 4.8 KB
- 📄 session-json-schema.md 3.6 KB
- 📄 ui-known-findings-schema.md 4.6 KB
- 📄 ui.md 17.0 KB
📄 SKILL.md 9.1 KB
SKILL.md

---
name: audit
description: "(ePost) Audit workflow — auto-detects UI component, a11y, or code audit"
user-invocable: true
metadata:
  argument-hint: "[--ui <ComponentName> [--platform web|ios|android|all] | --a11y [platform] | --code]"
  keywords: [audit, review, component, a11y, accessibility, code, quality, ui-lib, muji, tokens]
  triggers:
    - "audit"
    - "audit component"
    - "audit ui"
    - "audit a11y"
    - "audit code"
    - "code audit"
    - "component audit"
  platforms: [all]
  agent-affinity: [epost-muji, epost-code-reviewer, epost-a11y-specialist]
  connections:
    enhances: [code-review, ui-lib-dev]
    requires: [knowledge-retrieval]
---

# Audit — Unified Audit Command

Auto-detect and execute the appropriate audit workflow.

## Methodology Tracking

Every audit report MUST include a `methodology` field (JSON) or **Methodology** section (Markdown) documenting:
- **Files Scanned** — every file actually read
- **Knowledge Tiers** — which levels (L1–L5) were activated and whether each was available
- **Standards Source** — the skill files, checklists, and external standards used as rule authority
- **Coverage Gaps** — anything unavailable (RAG down, checklist not found, no platform rules loaded)

Track these as you work. Never leave them empty or with placeholder values.

## Knowledge Retrieval (Pre-Audit)

Before executing any audit mode, activate `knowledge-retrieval` to load relevant context:
- L1 `docs/` — existing conventions, past findings, ADRs for the files under review
- L2 RAG — component implementations, token definitions, usage patterns
- L4 Grep/Glob — fallback if RAG unavailable (search `packages/`, `src/` directly)
- L5 Context7 — library API verification for external dependency usage

**RAG unavailable?** Skip L2, go directly to L4 Grep/Glob. Never block the audit waiting for RAG.

## Subagent Constraint

**Subagents cannot spawn further subagents** — neither Agent tool nor Task tool is available in subagent context. Therefore, this skill runs **inline in the main conversation** (no `context: fork`). The main conversation is the orchestrator — it dispatches specialist agents and merges their results.

## Step 0 — Flag Override + Mode Selection

If `$ARGUMENTS` starts with `--ui`: **dispatch epost-muji** via Agent tool. Pass component name + platform flags + `references/ui.md` workflow.
If `$ARGUMENTS` starts with `--a11y`: **dispatch epost-a11y-specialist** via Agent tool. Pass `references/a11y.md` + platform hint.
If `$ARGUMENTS` starts with `--close --ui`: load `references/close-ui.md` and execute inline.
If `$ARGUMENTS` starts with `--close`: load `references/close-a11y.md` and execute inline.
If `$ARGUMENTS` starts with `--code`: **dispatch epost-code-reviewer** via Agent tool.
If auto-detected as **hybrid** (see Hybrid Detection below): run Hybrid Orchestration.
Otherwise: continue to Auto-Detection.

## Hybrid Detection

Trigger hybrid mode when ALL conditions met:
- Target contains klara-theme files (path contains `libs/klara-theme/` or `libs/common/`)
- File count >= 20 OR multiple subdirectories in scope
- No explicit `--ui` or `--code` flag (those force single-agent mode)

## Hybrid Orchestration (main context)

**This runs in the main conversation, NOT in a subagent.** The main context has Agent tool available.

```
session_folder = reports/{YYMMDD-HHMM}-{slug}-audit/
```

1. **Create session folder**: `Bash("mkdir -p {session_folder}")`
2. **Dispatch epost-muji** via Agent tool with Template A+ from `references/delegation-templates.md`:
   - Fill: Scope, Component(s), Mode: library, Platform, Output path: `{session_folder}/muji-ui-audit.md`
   - WAIT for muji to complete
3. **Read muji report** at `{session_folder}/muji-ui-audit.md`. Extract:
   - `finding_locations`: Set of file:line flagged by muji
   - `verdict`: muji's overall verdict
   - `a11y_findings`: contents of `## A11Y Findings` section (if present)
4. **If a11y findings exist**: dispatch epost-a11y-specialist via Agent tool (Template B):
   - Output path: `{session_folder}/a11y-audit.md`
   - WAIT for completion
5. **Dispatch epost-code-reviewer** via Agent tool:
   - Pass: file list, `{session_folder}/muji-ui-audit.md` path (for dedup), SEC/PERF/TS/ARCH/STATE/LOGIC scope
   - Output path: `{session_folder}/code-review-findings.md`
   - WAIT for completion
6. **Merge reports** into `{session_folder}/report.md`:
   - Executive Summary with overall verdict
   - `## UI Audit` — muji verdict, finding count, link to `muji-ui-audit.md`
   - `## A11Y Audit` (if ran) — link to `a11y-audit.md`
   - `## Code Review` — code-reviewer findings inline
   - Methodology section
6.5. **Run build verification**:
   ```bash
   node .claude/hooks/lib/build-gate.cjs
   ```
   Append `## Build Verification` section to `{session_folder}/report.md`:
   - Exit 0: `Build verification: ✓ PASS ({platform}, {duration_ms}ms)`
   - Exit 1: `Build verification: ✗ FAIL — {error excerpt}` (advisory — does not block report)
   - Exit 2: `Build verification: skipped (no build command detected)`
7. **Write session.json** per `references/session-json-schema.md`
8. **Update reports/index.json** per `core/references/index-protocol.md`

Verdict = `max(muji, a11y, code-reviewer)` where REDESIGN > FIX-AND-RESUBMIT > APPROVE.

## Single-Agent Delegation Protocol

For non-hybrid dispatches (`--ui`, `--code`, `--a11y`):

1. Create session folder per `references/output-contract.md`
2. Select template from `references/delegation-templates.md`
3. Fill all `{placeholders}` — include `Output path: {session_folder}/{filename}`
4. Dispatch via **Agent tool** to the specialist agent
5. **Wait** for specialist report
6. Run build verification: `node .claude/hooks/lib/build-gate.cjs` — append `## Build Verification` to report (advisory)
7. Write `session.json` and update `reports/index.json`

**Output contract**: `references/output-contract.md` is the single source of truth for paths and responsibilities.

| Template | Specialist | When |
|----------|-----------|------|
| A — UI Component Audit | epost-muji | `--ui` flag or UI component signals |
| B — A11y Audit | epost-a11y-specialist | `--a11y` flag or A11y findings from UI audit |
| C — Code Escalation | epost-code-reviewer | Critical findings needing deeper pass |
| D — Docs Gap Detection | epost-docs-manager | Post-audit, new feature, or refactor |
| E — MCP/RAG Query | epost-mcp-manager | Component catalog lookup, pattern search |

## Aspect Files

| File | Purpose |
|------|---------|
| `references/output-contract.md` | **Single source of truth** — all output paths, session folders, file names, agent responsibilities |
| `references/ui.md` | Audit UI component (Senior Muji Reviewer) |
| `references/a11y.md` | Audit staged changes for WCAG 2.1 AA violations |
| `references/close-a11y.md` | Mark an accessibility finding as resolved |
| `references/close-ui.md` | Close/resolve a UI finding in known-findings DB |
| `references/ui-known-findings-schema.md` | Schema for `.epost-data/ui/known-findings.json` |
| `references/session-json-schema.md` | Schema for `session.json` — per-session metadata written to every session folder |
| `references/delegation-templates.md` | Structured handoff templates for specialist delegation |

## Auto-Detection

Analyze `$ARGUMENTS` keywords and context:

| Signal | Dispatch |
|--------|----------|
| Component name (`Epost*`, UI keyword), "component", "ui-lib", "design system", "token", "klara", "muji" | `--ui` → `references/ui.md` via **epost-muji** |
| "a11y", "accessibility", "wcag", "voiceover", "talkback" | `--a11y` → `references/a11y.md` |
| "close" + "ui" signals | `--close --ui` → `references/close-ui.md` |
| "close", "resolve", "finding" | `--close` → `references/close-a11y.md` |
| "code", "security", "performance", staged changes without component signal | `--code` → `code-review` |
| Ambiguous | Ask: UI component audit, a11y audit, or code audit? |

## Platform Detection (--ui mode)

When delegating to epost-muji, detect target platforms:
- Explicit `--platform web|ios|android|all` in args → pass through
- `.swift` context → `--platform ios`
- `.kt`/`.kts` context → `--platform android`
- `.tsx`/`.jsx`/`.ts` context → `--platform web`
- No context → `--platform all`

## Variant Summary

| Flag | Agent | Reference | Scope |
|------|-------|-----------|-------|
| `--ui` | epost-muji | `references/ui.md` | Design system components (web/iOS/Android) |
| `--a11y` | epost-a11y-specialist | `references/a11y.md` | WCAG 2.1 AA violations |
| `--close` | epost-a11y-specialist | `references/close-a11y.md` | Mark a11y finding as resolved |
| `--close --ui <id>` | epost-muji | `references/close-ui.md` | Mark UI finding resolved |
| `--code` | epost-code-reviewer | `code-review` | General code quality, security, performance |

## Examples

- `/audit --ui EpostButton` → muji audits EpostButton across all platforms
- `/audit --ui EpostCard --platform web` → muji audits web-only
- `/audit --a11y` → a11y specialist audits staged changes
- `/audit --code` → reviewer audits staged code changes
- `/audit --close --ui 3` → mark UI finding ID 3 as resolved
- `/audit EpostInput` → auto-detected as UI audit → delegates to muji
Comments 0
Latest | Hot
Please login before commenting.
No comments yet. Be the first one!
audit

Directory Structure

SKILL.md

Report

Notice
