vittrade-minimal-review

Reviews Flutter diffs for over-engineering and suggests line-level simplifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flutter codebases accumulate bloat over time: local widgets that duplicate shared design-system primitives, abstractions with a single caller, and speculative wrappers that add lines without value. This Skill reviews a diff or batch of changes and flags exactly what to cut, keeping the codebase lean without touching safety-critical financial flows. ## Core Features & Use Cases - Over-Engineering Detection: Finds dead code, one-caller helpers, unused wrappers, and local widgets duplicating shared Vit* primitives, each tagged as delete, yagni, shrink, or reuse-vit. - Safety-Aware Scope: Explicitly skips financial preview/confirm flows, masked sensitive data, required migration work, and guardrail tests so trims never compromise correctness. - Batch Completion Gate: When triggered automatically at batch end, applies safe trims inline, re-runs flutter analyze and focused tests, and reports net lines saved. - Use Case: After finishing a feature batch in the VitTrade Flutter app, run the review to get findings like "L42: yagni helper with one caller. Inline it." and end with a shorter diff that still passes the plan gate. ## Quick Start Ask the assistant to run a minimal review on the current diff and list any bloat to trim before completing the batch.

Frequently Asked Questions about vittrade-minimal-review

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

FAQPage Schema
How do I review a Flutter diff for unnecessary complexity?

Run the minimal review on your current diff to get one finding per line with a tag: delete for dead code, yagni for single-caller abstractions, shrink for shorter equivalents, and reuse-vit for widgets duplicating shared Vit* primitives. Each finding names what to cut and its replacement.

What does the batch completion gate do automatically?

When triggered at batch completion without a user prompt, it lists findings only for that batch's diff, applies safe trims inline such as deleting wrappers or inlining one-caller helpers, then re-runs flutter analyze and focused tests before marking the batch complete.

Does the review flag financial or safety-critical code?

No. It explicitly skips financial preview and confirm flows, masked sensitive data, risk copy, required loading and error states, guardrail tests under flutter_app/test/quality/, and required migrations from local widgets to shared primitives.

When should I not use this minimal review skill?

Do not use it for correctness, security, or product-boundary bugs, which belong to the code-review-and-quality skill. It only addresses complexity and does not run whole-repo audits, focusing strictly on the current diff or batch.

What output format do the review findings use?

Each finding follows the format L<line>: <tag> <what>. <replacement>., or <file>:L<line> for multi-file diffs. The review ends with a score line stating net lines removable or Lean already. Ship.