knip-deadcode

Knip dead code detection best practices for JavaScript and TypeScript projects. Use when configuring Knip, analyzing unused code, setting up CI integration, or cleaning up codebases. Triggers on knip.

SKILL.md

GitHub

Community Knip Dead Code Detection Best Practices

Comprehensive guide for detecting and removing dead code in JavaScript and TypeScript projects using Knip. Contains 43 rules across 8 categories, prioritized by impact to guide configuration, CI integration, and cleanup workflows.

When to Apply

Reference these guidelines when:

  • Configuring Knip for a new project or monorepo
  • Investigating false positives or false negatives
  • Setting up CI pipelines to prevent dead code regressions
  • Using auto-fix to clean up unused code
  • Optimizing Knip performance for large codebases

Rule Categories by Priority

Priority Category Impact Prefix
1 Configuration Foundations CRITICAL config-
2 Entry Point Strategy CRITICAL entry-
3 Workspace & Monorepo HIGH workspace-
4 Dependency Analysis HIGH deps-
5 Export Detection MEDIUM-HIGH exports-
6 CI Integration MEDIUM ci-
7 Auto-Fix Workflow MEDIUM fix-
8 Performance Optimization LOW-MEDIUM perf-

Quick Reference

1. Configuration Foundations (CRITICAL)

2. Entry Point Strategy (CRITICAL)

3. Workspace & Monorepo (HIGH)

4. Dependency Analysis (HIGH)

5. Export Detection (MEDIUM-HIGH)

6. CI Integration (MEDIUM)

7. Auto-Fix Workflow (MEDIUM)

8. Performance Optimization (LOW-MEDIUM)

How to Use

Read individual reference files for detailed explanations and code examples:

Reference Files

File Description
references/_sections.md Category definitions and ordering
assets/templates/_template.md Template for new rules
metadata.json Version and reference information