ai-bundle-check_skill

Overview

This skill analyzes your build output and tells you exactly what is inflating your bundle and how to reduce it. It combines static inspection of package files and compiled assets with AI-driven recommendations to highlight the biggest offenders and concrete fixes. Use it with minimal setup—one command and no configuration required.

How this skill works

The tool scans package metadata and your build directory to compute size contributions per file and dependency. It identifies large modules, unused exports, and patterns that prevent tree-shaking, then sends a focused analysis to an AI model which returns prioritized suggestions like swapping libraries, changing import styles, or enabling code splitting. Results include a ranked breakdown, actionable fixes, and command examples to implement optimizations.

When to use it

• Your app loads slowly and you suspect bundle size is the cause
• Before shipping a release to catch unexpected size regressions
• After adding a new dependency to assess its impact
• When CI flags a bundle size threshold breach
• During performance audits to get concrete optimization steps

Best practices

• Run the checker early and often—integrate into CI to detect regressions
• Prefer lightweight alternatives (example: date-fns over moment) when feasible
• Use dynamic imports and code splitting for rarely used features
• Enable and verify tree-shaking by using ES module imports
• Review AI suggestions and apply the smallest safe change first, then re-measure

Example use cases

• Quickly find which dependency added 500KB to a new release
• Identify unused exports blocking tree-shaking in a large bundle
• Compare two builds to see what changed between commits
• Generate a prioritized list of fixes before a performance sprint
• Automate a CI step that fails a build when bundle size increases