Identify unused files, dependencies, and exports in JavaScript/TypeScript projects.
npx skills add https://github.com/knoopx/pi --skill knip-knoopx
Please help me install this Agent Skill. Skill: knip Source: https://github.com/knoopx/pi/tree/main/agent/skills/knip Command: npx skills add https://github.com/knoopx/pi --skill knip-knoopx
This Skill helps developers quickly identify and remove unused files, dependencies, and exports in JavaScript and TypeScript projects, reducing bundle size and technical debt.
Use bunx knip to analyze a project. bunx knip # Analyze project bunx knip --production # Production only (no tests, devDeps) bunx knip --strict # Direct dependencies only bunx knip --fix # Auto-remove unused (use cautiously) bunx knip --include files # Only unused files bunx knip --include exports # Only unused exports bunx knip --include dependencies # Only unused deps
High-intent search queries and answers about installing and using this skill.
To find unused dependencies and dead code in a JavaScript or TypeScript monorepo, use a static analysis tool to scan project graphs. This identifies unreferenced files, stale dependencies, and unused exports across multiple workspaces.
The best way to prune unused exports from a TypeScript project is by running static analysis to surface unreferenced modules. You can then manually remove them or use automated flags to clean up the codebase.
Yes, you can automatically remove unused files and dependencies from package.json by running the analysis tool with an auto-fix flag. This prunes stale dependencies and dead files, though it should be used cautiously.
Static analysis for dead code does work with production builds by using a production-only flag. This excludes tests and devDependencies from the scan, focusing strictly on direct dependencies used in the live environment.
To only scan for unused dependencies without checking exports or files, run the analysis tool with an include flag specifically set for dependencies. This restricts the output to only show stale package.json entries.
You should use static analysis to detect unreferenced exports in Node.js because it reduces bundle size and technical debt. Scanning project graphs provides actionable results to safely clean up dead code across packages.
Q16GMap technology stacks, architecture layers, and entry points into a project-framework diagram.
SocketDevIdentifies and classifies unused or dead API export subpaths in libraries via fleet-wide analysis.
wyattowalshEnforces JavaScript/TypeScript development conventions with pnpm for Node.js projects.
roderikIdentify and remove unused files, dependencies, and exports in JavaScript/TypeScript projects.
