skills.rest
MaxWolf-01
MaxWolf-01COMMUNITY
Explore all skills by this author →
Website𝕏@MaxWolf_01GitHub

bloat-audit

Audits a repository for over-engineering and produces a ranked list of code to delete or simplify.

3|Updated Jan 10, 2026
Search Tags:#code review#refactoring#code audit#dead code#simplification#over-engineering#dependency cleanup
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill bloat-audit-maxwolf-01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bloat-audit
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/bloat-audit
Command: npx skills add https://github.com/MaxWolf-01/agents --skill bloat-audit-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate dead code, redundant dependencies, and speculative abstractions that increase maintenance cost. This Skill performs a whole-repo audit that reads every source file and dependency, then reports exactly what to cut, ranked by impact. ## Core Features & Use Cases - Tagged Findings: Classifies each issue as delete, stdlib, native, yagni, or shrink, with a concrete replacement for every cut. - Ranked Report: Outputs one line per finding ordered biggest cut first, ending with a net line and dependency savings estimate. - Report-Only Scope: Audits without modifying code, so the reader decides which cuts to apply. - Use Case: Before a refactor sprint, run the audit on a legacy service to find hand-rolled utilities the standard library already provides, single-implementation abstractions, and unused config flags. ## Quick Start Ask the agent to run a bloat audit on this repository and report the ranked list of cuts.

Frequently Asked Questions about bloat-audit

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

FAQPage Schema
How do I find dead code and over-engineering in my repository?▼

Run a whole-repo bloat audit that reads every source file and dependency, then flags dead code, unused flexibility, and speculative features. Findings are tagged and ranked biggest cut first so you can prioritize deletions.

How to identify dependencies replaceable by the standard library?▼

The audit tags these as stdlib or native findings and names the exact replacement, such as Intl.DateTimeFormat instead of moment.js. Each finding includes the file path and line for quick verification.

Does the bloat audit modify or delete my code automatically?▼

No, the audit is report-only by design. It produces a ranked list of recommended cuts, and the reader decides which findings to apply as a separate step.

What kinds of issues are out of scope for a bloat audit?▼

Correctness, security, and performance problems are explicitly routed to a normal review pass. The audit covers only over-engineering: dead code, redundant abstractions, and replaceable dependencies.

When is a bloat audit not the right tool?▼

It is not suited for finding bugs, vulnerabilities, or slow code, since those require correctness and performance review. It also will not flag a lone smoke test or minimal self-check, which it treats as the lean minimum.

Related Skills

Explore More Software Engineering Skills→
MDSIXONEMDSIXONE

clonedeps

Clone dependency source repositories into an ignored local workspace for agent inspection.

Community
Advanced
microsoftmicrosoft
1.4k

prompt-refactor

Refactors prompt-engineering artifacts through the hve-builder refactor route while preserving behavior.

Official
Intermediate
CuriousLearnerCuriousLearner
27

dead-code-detector

Detects and categorizes unused code, imports, and dependencies in six programming languages.

Community
Advanced
acardozzoacardozzo

clean-rx

Analyze Python, Next.js, and Supabase codebases for dead code and generate prioritized deletion plans.

Community
Advanced