bundle-checker

What This Skill Does

The bundle-checker skill is an advanced diagnostic tool designed to help developers optimize their front-end performance by analyzing build artifacts. It scans your project directory and build output to identify 'bundle bloat'—the unnecessary accumulation of JavaScript or CSS dependencies that slow down application load times. By leveraging GPT-4o-mini, the skill parses your package.json and actual build files to pinpoint the largest contributing dependencies. Beyond simple identification, it provides actionable advice, such as recommending tree-shaking configurations, suggesting lightweight alternatives to heavy libraries (e.g., date-fns over moment.js), and identifying candidates for dynamic imports. This skill effectively turns complex build data into a prioritized task list for performance optimization.

Installation

To integrate this skill into your OpenClaw environment, use the provided command in your terminal. This adds the tool to your toolkit, allowing the AI agent to execute the analysis directly within your development context.

clawhub install openclaw/skills/skills/lxgicstudios/ai-bundle-check

Ensure that you have an active OPENAI_API_KEY environment variable set, as the tool relies on the AI engine to generate its specific optimization insights.

Use Cases

• Performance Audits: Quickly identify why a production build exceeds acceptable size thresholds.
• Dependency Vetting: Run the tool before and after adding a new library to measure its precise impact on your final bundle size.
• CI/CD Optimization: Automate bundle size checks within your deployment pipeline to catch size regressions before they reach production.
• Legacy Refactoring: Determine which older dependencies can be replaced with modern, modular alternatives to significantly reduce load times.

Example Prompts

1. "Analyze my current project bundle and tell me which three dependencies are the largest contributors to the bloat."
2. "I'm getting a high bundle size warning in my build. Can you run the bundle-checker and suggest specific tree-shaking optimizations?"
3. "Run a detailed breakdown of the ./dist directory and suggest lighter alternatives for my current date and utility libraries."

Tips & Limitations

• Run Regularly: Don't wait for your bundle to become problematic; check it periodically to maintain optimal performance.
• Environment: The tool requires Node.js 18+ to run effectively.
• Context is Key: Ensure you are running the tool from the root of your project so it can accurately read your package.json and build artifacts.
• AI Dependency: The tool relies on external API calls; ensure your network environment allows traffic to OpenAI endpoints for analysis.