القائمة
Compiles statistics from audit reports: PASS/PARTIAL/FAIL rates, most violated patterns, most failing DoD checks, and quality trends. Use after running several audits to spot improvement areas.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. Use after implementation to verify quality before shipping.
Audits implementation against its DoD and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Use after implementation to verify quality before shipping.
Implements a feature from its spec following all guardrails: budget, DoD, anti-scope, and pattern compliance. Runs an 8-phase pipeline (find spec → extract guardrails → load patterns → plan → implement → test → refine → self-verify DoD). Use after gen-spec when you're ready to code. The agent has filesystem access and acts as Coding Agent.
Implements a feature from its spec with guardrails: budget, DoD, anti-scope, and pattern compliance. Runs an 8-phase pipeline (find spec → extract guardrails → load patterns → plan → implement → test → refine → self-verify DoD). Use after gen-spec when ready to implement.
Deep-analyzes the current codebase to discover stack, architecture, patterns, conventions, and pitfalls. Creates curated documentation in .vibeflow/ that persists and can be committed to git. Supports incremental updates, scoped deep-dives, interactive review, and satellite repo analysis. Use when setting up a project, after significant changes, or to deep-dive into a specific module.
Generates a technical spec with objective, Definition of Done (3–7 binary checks), scope, anti-scope, technical decisions, and applicable patterns. Grounded in the project's real patterns from .vibeflow/. Auto-splits specs that exceed budget or DoD limits. Use when requirements are clear and you're ready to define the implementation contract.
| name | vibeflow-stats |
| description | Compiles statistics from audit reports: PASS/PARTIAL/FAIL rates, most violated patterns, most failing DoD checks, and quality trends. Use after running several audits to spot improvement areas. |
Show statistics from audit reports. Reads all audits and compiles pass/fail rates, most violated patterns, and common DoD gaps.
Usage: Run this skill with no input. It reads .vibeflow/audits/.
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.
Check if .vibeflow/audits/ directory exists and contains .md files.
Read ALL .md files in .vibeflow/audits/.
For each audit file, extract:
**Verdict:** line)[x] and failed [ ] checkboxes
in the ### DoD Checklist section[ ] in the ### Pattern Compliance
section, with the pattern name### 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.>