What problem does it solve? Lint and tests only read the repository, so they never reveal what actually ships in an npm tarball. This Skill performs the final pre-publish audit by reading the real packed inventory, catching files that must not ship, missing files, broken entry points, and documentation claims that no longer match the package. ## Core Features & Use Cases - Tarball Inventory Reading: Runs npm pack --dry-run and reads every line of the output, treating the inventory as the only true statement of what ships rather than trusting the files: allowlist. - Entry Point Verification: Installs the packed tarball into an empty project and resolves main, exports, bin, and types from the consumer's side, since a path that resolves in the repository can be absent in the tarball. - Documentation and Policy Scanning: Walks the README's own instructions against reality and greps for project-specific rules no linter enforces, such as forbidden names or frozen files. - Use Case: Before publishing a new version of an internal library, run this audit to confirm the tarball contains the built output, excludes test fixtures, and that the README's install command and examples still match the package. ## Quick Start Audit this package before publishing by running npm pack --dry-run, reviewing the full file inventory, and verifying the entry points resolve from a fresh install.
