home / skills / openclaw / skills / ai-bundle-check

ai-bundle-check skill

/skills/lxgicstudios/ai-bundle-check

This skill analyzes your bundle, identifies space hogs, and provides AI-driven recommendations to reduce size and improve load times.

npx playbooks add skill openclaw/skills --skill ai-bundle-check

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.2 KB
---
name: bundle-checker
description: Analyze bundle size and get AI suggestions to reduce it. Use when your builds are getting bloated.
---

# Bundle Checker

Your bundle is 2MB and you don't know why. This tool analyzes your build output and tells you exactly what's eating up space and how to fix it.

**One command. Zero config. Just works.**

## Quick Start

```bash
npx ai-bundle-check
```

## What It Does

- Analyzes your bundle composition
- Identifies the largest dependencies
- Suggests tree-shaking opportunities
- Recommends lighter alternatives

## Usage Examples

```bash
# Analyze current project
npx ai-bundle-check

# Analyze specific directory
npx ai-bundle-check ./my-project/

# Get detailed breakdown
npx ai-bundle-check --verbose
```

## Best Practices

- **Check before shipping** - catch size regressions early
- **Consider alternatives** - moment.js vs date-fns makes a huge difference
- **Dynamic imports** - split code that isn't needed immediately
- **Monitor trends** - track bundle size in CI

## When to Use This

- Your app loads slowly and you suspect the bundle
- Adding a new dependency and want to check the impact
- Performance audit flagged JavaScript size
- CI bundle size check is failing

## Part of the LXGIC Dev Toolkit

This is one of 110+ free developer tools built by LXGIC Studios. No paywalls, no sign-ups, no API keys on free tiers. Just tools that work.

**Find more:**
- GitHub: https://github.com/LXGIC-Studios
- Twitter: https://x.com/lxgicstudios
- Substack: https://lxgicstudios.substack.com
- Website: https://lxgicstudios.com

## Requirements

No install needed. Just run with npx. Node.js 18+ recommended. Needs OPENAI_API_KEY environment variable.

```bash
npx ai-bundle-check --help
```

## How It Works

Scans your package.json and build output, identifies heavy dependencies, and sends the analysis to GPT-4o-mini. The AI knows common bundle bloat patterns and suggests specific optimizations like switching libraries or adding tree-shaking config.

## License

MIT. Free forever. Use it however you want.

---

**Built by LXGIC Studios**

- GitHub: [github.com/lxgicstudios/ai-bundle-check](https://github.com/lxgicstudios/ai-bundle-check)
- Twitter: [@lxgicstudios](https://x.com/lxgicstudios)

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

FAQ

Do I need special configuration to run it?

No—one command runs with sensible defaults. You can pass a path or verbosity flags for more detail.

Does it modify my code automatically?

No—the tool provides recommendations and code examples. Apply changes yourself or via your preferred automation.