bundle-analysis
Bundle analysis. Use when measuring current bundle size, comparing stable or selected fixtures, inspecting composition, or cleaning retained comparison state.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- bundle-analysis
- description
- Bundle analysis. Use when measuring current bundle size, comparing stable or selected fixtures, inspecting composition, or cleaning retained comparison state.
03 SKILL.md 正文
Read packages/tools/bundle/README.md, then select one workflow:
- Stable comparison:
pnpm bundle-compare <base-ref>. UseHEAD~1for the latest commit. Readtmp/bundle-stats.txtand report non-zero differences. - Selected comparison:
pnpm bundle-compare-selected --base <ref> scratchpad/<fixture>.ts. Use only user-named or investigation-local fixtures; keep temporary fixtures out of the stable corpus. - Composition:
pnpm bundle-analyze scratchpad/<fixture>.ts. Read raw data first and report the largest modules, dependency groups, and surprising inclusions. Its readable-name output is not an exact size measurement. - Current size: Build immediately before the direct bundle report so Effect
packages resolve from current
distoutput. - Cleanup: Stable comparisons retain
tmp/bundle-basefor reuse unless cleanup is requested. Remove selected-comparison state retained with--keep-baseafter its final use. Verify cleanup without disturbing unrelated worktrees.
The task is complete when the selected artifact is inspected, requested size or composition findings are reported, generated paths are named, and comparison state follows the selected workflow's retention policy.
04 同仓库更多 Skills
vendored-assets
Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.
test-development
Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.
pull-requests
Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one.
performance-analysis
Performance analysis. Use for runtime throughput or latency benchmarks, TypeScript compiler cost, performance regressions, comparison harnesses, or thresholds.
package-development
Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path.
migration-guidance
Use when changing how a v3 public API maps to v4, editing migration annotations, or regenerating migration/v3-to-v4.md.