package

Remove build artifacts, dependencies, and secrets before packaging Node.js TypeScript projects for distribution.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ys0714/ecom-agent --skill package-ys0714
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package
Source: https://github.com/ys0714/ecom-agent/tree/main/.claude/skills/package
Command: npx skills add https://github.com/ys0714/ecom-agent --skill package-ys0714

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates cleaning build artifacts, caches, IDE files, and local secrets so the repository can be safely packaged and shared without leaking credentials or unnecessary files.

Core Features & Use Cases

  • Safe sanitization: Remove node_modules, dist, coverage, local agent data, and editor swap files to reduce package size and surface area.
  • Secret cleanup: Delete local environment files and specific skill caches to prevent accidental exposure of API keys and sensitive data.
  • Use Case: Before creating a release tarball or handing the project to external reviewers, run this pipeline to produce a minimal, non-sensitive distribution bundle.

Quick Start

Run the package skill to remove local artifacts and sanitize secrets before preparing the repository for distribution.

Frequently Asked Questions about package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean a Node.js repository for safe distribution?

Cleaning a Node.js repository for safe distribution involves removing node_modules, build outputs, coverage, and IDE files, then deleting local environment files and caches to prevent accidental exposure of API keys and sensitive data.

What is the best way to remove secrets and environment files before a release?

Removing secrets and environment files before a release requires deleting local environment files and specific skill caches, ensuring API keys and sensitive data are not included in the final distribution bundle.

How do I prepare a TypeScript project for handoff to external reviewers?

To prepare a TypeScript project for handoff to external reviewers, run a cleanup pipeline that removes local artifacts, editor swap files, and agent data to produce a minimal, non-sensitive distribution bundle.

Does the repository cleanup process verify project integrity after removing artifacts?

The repository cleanup process verifies project integrity by reinstalling dependencies and running tests after removing node_modules, dist, coverage, and local environment files.

Can I use this cleanup pipeline for CI environment sanitization?

You can use this cleanup pipeline for CI cleanup scenarios, as it safely removes build artifacts, caches, and local secrets to reduce package size and surface area for continuous integration workflows.