How do I install the Compare Array Bundle Size skill?

Run npx skillmds@latest add posthog-posthog-js/compare-array-bundle-size in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Compare Array Bundle Size safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Compare Array Bundle Size?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Compare Array Bundle Size free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Compare Array Bundle Size?

PostHog (@posthog-posthog-js) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Compare Array Bundle Size by posthog-posthog-js

Name: Compare Array Bundle Size
Rating: 4.2 (5 reviews)
Author: PostHog

Compare Array Bundle Size

Quickly compare the posthog-js array.js bundle size in the current working tree against a git baseline using the repository's esbuild proxy. Use when asked about array.js size, bundle-size percentage changes, whether browser SDK changes increased the bundle, or for a fast size check that should not run the production Rollup build.

PostHog Updated Sep 10, 2026

File contents

Compare `array.js` bundle size

Use the repository's fast comparison command. Do not run TypeScript compilation, Terser, Rollup, Turbo, or the full build unless the user separately requests production bundle numbers.

Workflow

Use the baseline named by the user. If none is given, let the script default to origin/main and then main.
From the repository root, run:
```
pnpm bundle-size:array [baseline-ref]
```
Report:
- the resolved baseline ref and commit
- minified percentage and byte change
- gzip percentage and byte change
- Brotli percentage and byte change
- elapsed time
Lead with the percentage most relevant to the user's question. If they did not specify one, lead with minified and include the compressed results below it.

Interpretation

The command builds both source trees with the same esbuild version, options, installed dependencies, and workspace-source aliases, so the percentage is an apples-to-apples comparison.
The current side includes tracked, uncommitted, and imported untracked source changes from the working tree.
The baseline side is a temporary source snapshot from the resolved git commit; the command does not check out or modify the working tree.
Treat the result as a fast directional comparison. Absolute bytes differ from the production Rollup/Terser output.
A positive percentage is a size increase; a negative percentage is a reduction.

Validation and troubleshooting

To verify the comparison machinery itself, run pnpm bundle-size:array HEAD. With no relevant uncommitted source changes, every row should report 0.00%.
If the baseline ref cannot be resolved, ask for another local git ref or fetch it only with the user's approval when network access is required.
If esbuild or other dependencies are missing, explain that dependencies must be installed. Do not substitute the full production build.

---name: compare-array-bundle-sizedescription: Quickly compare the posthog-js array.js bundle size in the current working tree against a git baseline using the repository's esbuild proxy. Use when asked about array.js size, bundle-size percentage changes, whether browser SDK changes increased the bundle, or for a fast size check that should not run the production Rollup build.---# Compare `array.js` bundle sizeUse the repository's fast comparison command. Do not run TypeScript compilation, Terser, Rollup, Turbo, or the full build unless the user separately requests production bundle numbers.## Workflow1. Use the baseline named by the user. If none is given, let the script default to `origin/main` and then `main`.2. From the repository root, run: ```bash pnpm bundle-size:array [baseline-ref] ```3. Report: - the resolved baseline ref and commit - minified percentage and byte change - gzip percentage and byte change - Brotli percentage and byte change - elapsed time4. Lead with the percentage most relevant to the user's question. If they did not specify one, lead with minified and include the compressed results below it.## Interpretation- The command builds both source trees with the same esbuild version, options, installed dependencies, and workspace-source aliases, so the percentage is an apples-to-apples comparison.- The current side includes tracked, uncommitted, and imported untracked source changes from the working tree.- The baseline side is a temporary source snapshot from the resolved git commit; the command does not check out or modify the working tree.- Treat the result as a fast directional comparison. Absolute bytes differ from the production Rollup/Terser output.- A positive percentage is a size increase; a negative percentage is a reduction.## Validation and troubleshooting- To verify the comparison machinery itself, run `pnpm bundle-size:array HEAD`. With no relevant uncommitted source changes, every row should report `0.00%`.- If the baseline ref cannot be resolved, ask for another local git ref or fetch it only with the user's approval when network access is required.- If esbuild or other dependencies are missing, explain that dependencies must be installed. Do not substitute the full production build.

Frequently asked questions