Individual skill
audit-bundles
Analyze a pracht production build for client bytes per route, heavy vendor chunks, and large dependencies, and recommend code-splitting and prefetch changes. Use for "audit bundles", "why is my JS so big", "bundle size per route", "what's in my vendor chunk".
skills/audit-bundles/SKILL.md
Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 106
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- cloudflare-workers Repository topic
- framework Repository topic
- full-stack Repository topic
- llms-txt Repository topic
- mcp Repository topic
- preact Repository topic
- ssg Repository topic
- ssr Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Pracht Audit Bundles
pracht performs route-level code splitting via the Vite plugin and emits a
manifest. This skill reads that manifest, sizes each route's client payload,
and surfaces the worst offenders.
## Step 1: Build with analysis
MCP: if `pracht dev-mcp` is registered, prefer its `inspect_*`, `doctor`, and `verify` tools to the CLI.
`pracht inspect build` needs a prior `pracht build`.
```bash
pracht build --analyze --json
```