stats - SKILL.md Agent Skill

name: stats description: > Compiles statistics from audit reports: PASS/PARTIAL/FAIL rates, most violated patterns, most failing DoD checks, and quality trends over time. Output is chat-only (no file created). Use after running several audits to spot quality patterns and improvement areas. allowed-tools: Read, Grep, Glob

Description and examples

What it does: Scans .vibeflow/audits/, aggregates verdicts (PASS/PARTIAL/FAIL), which patterns are most often violated, and which DoD checks fail most. Output is in the chat only (no file). Use after you have at least a few audits.

Examples:

/vibeflow:stats — No arguments; reports summary of all audits in .vibeflow/audits/.

Language

Detect the language of the user's conversation context. Write ALL output in that same language. Technical terms in English are acceptable regardless of the detected language.

Compile and report statistics from audit reports.

Steps

Check if .vibeflow/audits/ directory exists and contains .md files.
- If no audits found: report "No audits found. Run /vibeflow:audit after implementing a feature." and STOP.
Read ALL .md files in .vibeflow/audits/.
For each audit file, extract:
- Verdict: PASS, PARTIAL, or FAIL (from the **Verdict:** line)
- DoD checks: count of passed [x] and failed [ ] checkboxes in the ### DoD Checklist section
- Pattern violations: items marked [ ] in the ### Pattern Compliance section, with the pattern name
- Convention violations: items listed in ### Convention Violations section (if present)
Compile the statistics and report directly in the chat (do NOT save to file). Use this format:

## Vibeflow Stats

**Audits analyzed:** N

### Verdicts
- PASS: N (X%)
- PARTIAL: N (X%)
- FAIL: N (X%)

### DoD
- Total checks: N
- Pass rate: X%
- Most failing checks:
  1. "<check description>" — failed N times
  2. "<check description>" — failed N times
  3. "<check description>" — failed N times

### Patterns
- Most violated patterns:
  1. <pattern name> — N violations
  2. <pattern name> — N violations
  3. <pattern name> — N violations

### Convention Violations
- Total: N violations across N audits
- Most common: <list top 3 if available>

### Trend
<If ≥3 audits exist, note if quality is improving (more PASS over time),
stable, or degrading. Base on chronological order of audit dates.>

If there are fewer than 3 audits, skip the "Trend" section. If there are no pattern violations, write "No pattern violations."

Rules

This command is READ-ONLY. It does NOT modify any files.
Output goes directly to the chat, not to a file.
Keep the report concise (~20-30 lines).
If audit files have non-standard format, extract what you can and note: "Non-standard format detected in ."

Maintenance

If this command is modified, update MANUAL.md to reflect the changes.