bundle-safety

What problem does it solve?

This Skill eliminates the risk of bundle transform changes (such as minification flag adjustments or re-export logic updates) silently breaking hard production constraints, including identifier guardrails, stack trace readability, and namespace re-export tracking, which can cause undetected runtime failures and broken build outputs.

Core Features & Use Cases

• Identifier-Preserving Minification Guidance: Enforces the standard --minify-whitespace --minify-syntax configuration to avoid breaking 13 grep guardrail assertions and preserve readable stack traces for debugging, while rejecting full identifier mangling that violates these constraints.
• Pre-Merge Consumer Constraint Verification: Provides a step-by-step procedure to test proposed transform changes against the smallest possible bundle and run all guardrail tests before merging, preventing broken changes from reaching production.
• Namespace Re-Export Coverage Checks: Ensures both regular (export * from './module') and aliased (export * as ns from './module') namespace re-export forms are tracked correctly to avoid silent gaps in repo-graph analysis.
• Use Case: For example, if a developer wants to enable full identifier mangling to reduce bundle size further, this Skill guides them to first verify no eval() dispatch or Function.name introspection exists in production paths, run all 13 grep guardrail tests, and confirm runtime stack trace readability before proceeding.

Quick Start

Use the bundle-safety skill to validate your proposed esbuild minification or re-export tracking changes against all required guardrails and conformance tests before merging the update.