ponytail-audit

Audits Flutter modules for over-engineering and ranks delete, yagni, shrink, and reuse findings.

Updated May 19, 2026
One-click install
npx skills add https://github.com/LonelyTraderBay/vittrade-flutter --skill ponytail-audit-lonelytraderbay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail-audit
Source: https://github.com/LonelyTraderBay/vittrade-flutter/tree/main/.agents/skills/ponytail-audit
Command: npx skills add https://github.com/LonelyTraderBay/vittrade-flutter --skill ponytail-audit-lonelytraderbay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flutter feature modules accumulate dead code, single-use abstractions, and widgets that duplicate the shared design system, inflating maintenance cost. This Skill scans a scope directory and produces a ranked ledger of over-engineering findings without touching the code. ## Core Features & Use Cases - Ranked Findings Ledger: Outputs one line per finding tagged as delete, yagni, shrink, or reuse-vit, ordered by token and debt savings. - Scoped Scanning: Defaults to the trade module's pages and widgets directories, with support for any user-named module path. - Token Drift Detection: Flags raw BorderRadius and hex colors used outside the shared design tokens. - Use Case: Once per sprint, run the audit on the trade module to get a markdown ledger in flutter_app/run-artifacts/ that the team schedules into later refactoring batches. ## Quick Start Run a ponytail audit on the trade module and write the ranked findings ledger to flutter_app/run-artifacts/.

Frequently Asked Questions about ponytail-audit

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

FAQPage Schema
How do I audit a Flutter module for over-engineering?

Run the ponytail audit against the module's pages and widgets directories. It scans for dead code, single-use abstractions, and duplicated shared widgets, then writes a ranked findings ledger to flutter_app/run-artifacts/ as a markdown file.

What does the ponytail audit flag in Flutter code?

It flags four categories: delete for dead code and unused wrappers, yagni for single-caller abstractions, shrink for logic expressible in fewer lines, and reuse-vit for local widgets duplicating shared Vit design-system components.

Does the audit refactor code automatically?

No. The audit is ledger-only by design. It writes findings to a dated markdown file in flutter_app/run-artifacts/, and fixes are scheduled in later batches rather than applied during the audit turn.

What code does the audit intentionally not flag?

It skips financial preview and confirm flows, masked data handling, required flow states, migrations from local widgets to shared Vit components, and guardrail tests under flutter_app/test/quality/.

How often should I run a code complexity audit?

The recommended cadence is roughly once per sprint on the active module. The trade module is the default first target, with home and wallet modules covered on rotation.