stats

Compile audit report statistics to identify PASS/PARTIAL/FAIL rates and violated patterns.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/pe-menezes/vibeflow-claude --skill stats-pe-menezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stats
Source: https://github.com/pe-menezes/vibeflow-claude/tree/main/skills/stats
Command: npx skills add https://github.com/pe-menezes/vibeflow-claude --skill stats-pe-menezes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand the quality of your development process by analyzing past audit reports, identifying recurring issues, and tracking improvements over time.

Core Features & Use Cases

  • Audit Aggregation: Compiles statistics from multiple audit reports.
  • Issue Identification: Pinpoints the most frequently failed Definition of Done (DoD) checks and violated patterns.
  • Quality Trend Analysis: Assesses whether code quality is improving, stable, or degrading based on historical data.
  • Use Case: After implementing several features and running audits, use this Skill to get a clear overview of common pitfalls and track progress in code quality.

Quick Start

Run the stats skill to see a summary of all your past audits.

Frequently Asked Questions about stats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track code quality trends from past audit reports?

Analyzing audit quality trends involves compiling statistics from past audit reports to identify PASS, PARTIAL, and FAIL rates over time. This process pinpoints the most frequently failed DoD checks and tracks whether code quality is improving or degrading.

What is the best way to identify frequently violated patterns in code audits?

To identify frequently violated patterns, you aggregate multiple audit reports to pinpoint the most failed Definition of Done checks. This reveals recurring issues and common pitfalls across your development process.

How many audit reports do I need for meaningful quality trend analysis?

For meaningful quality trend analysis, you need at least a few audit reports stored in the `.vibeflow/audits/` directory. A chronological history of these audits is required to calculate accurate PASS, PARTIAL, and FAIL rates over time.

Does audit quality analysis work without past audit files saved on disk?

Audit quality analysis does not work without past audit files saved on disk. The Skill requires at least a few audits stored in the `.vibeflow/audits/` directory to compile statistics and identify quality trends over time.

Can I export my code quality statistics and audit trend reports?

No, you cannot export code quality statistics and audit trend reports. The analysis output is chat-only, providing a summary of PASS, PARTIAL, and FAIL rates directly in your conversation without generating external files.