knip
Run knip to find and remove unused files, dependencies, and exports. Use for cleaning up dead code and unused dependencies.
What this skill does
# Knip Code Cleanup Run knip to find and remove unused files, dependencies, and exports from this codebase. ## Setup 1. Check if knip is available: - Run `npx knip --version` to test - If it fails or is very slow, check if `knip` is in package.json devDependencies - If not installed locally, install with `npm install -D knip` (or pnpm/yarn equivalent based on lockfile present) 2. If no `knip.json` or `knip.jsonc` config exists and knip reports many false positives, consider creating a minimal config based on the frameworks detected in package.json ## Execution 1. Run `npx knip` to get initial report 2. Review the output categories: - **Unused files** - files not imported anywhere - **Unused dependencies** - packages in package.json not imported - **Unused devDependencies** - dev packages not used - **Unused exports** - exported functions/variables not imported elsewhere - **Unused types** - exported types not used ## Cleanup Strategy ### Auto-delete (high confidence): - Unused exports that are clearly internal (not part of public API) - Unused type exports - Unused dependencies (remove from package.json) - Unused files that are clearly orphaned (not entry points, not config files) For these, proceed with deletion without asking. Use `--fix --allow-remove-files` for automated fixes, or manually delete/edit as needed. ### Ask first (needs clarification): - Files that might be entry points or dynamically imported - Exports that might be part of a public API (index.ts, lib exports) - Dependencies that might be used via CLI or peer dependencies - Anything in paths like `src/index`, `lib/`, or files with "public" or "api" in the name Use the AskUserQuestion tool to clarify before deleting these. ## Workflow 1. Run knip, capture full output 2. Categorize each issue as auto-delete or needs-clarification 3. Ask about uncertain items in a single batch question 4. Perform all deletions (use Edit tool to remove exports, Bash to remove files/deps) 5. Re-run knip to verify cleanup is complete 6. Repeat until no issues remain or only intentionally-ignored items exist ## Common Commands ```bash # Basic run npx knip # Production only (ignore test files) npx knip --production # Auto-fix what's safe npx knip --fix # Auto-fix including file deletion npx knip --fix --allow-remove-files # JSON output for parsing npx knip --reporter json ``` ## Notes - If knip config exists, respect its ignore patterns - Watch for monorepo setups - may need `--workspace` flag - Some frameworks need plugins enabled in config - Re-run after each batch of fixes to catch newly-exposed unused code
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.