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.json, dead code, unused exports, unused dependencies, bundle optimization.
- Installs
- 381
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pproenca/dot-skills --skill knip-deadcode- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads knip-deadcode automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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)
config-avoid-broad-ignore- Avoid broad ignore patternsconfig-configure-path-aliases- Configure path aliases in Knipconfig-enable-plugins-explicitly- Enable framework plugins explicitlyconfig-run-without-config- Run without config first for baselineconfig-separate-entry-project- Separate entry files from project filesconfig-use-json-schema- Use JSON schema for configuration validationconfig-use-negation-patterns- Use negation patterns for exclusionsconfig-use-production-mode- Use production mode for shipping code analysis
2. Entry Point Strategy (CRITICAL)
entry-add-dynamic-imports- Add dynamic import targets as entry pointsentry-exclude-test-files- Exclude test files from production entriesentry-include-all-entry-points- Include all application entry pointsentry-include-bin-scripts- Include binary scripts as entry pointsentry-use-compilers- Use compilers for non-standard file typesentry-use-plugin-entries- Use plugin entry points for frameworksentry-verify-with-debug- Verify entry points with debug mode
3. Workspace & Monorepo (HIGH)
workspace-configure-root-workspace- Configure root workspace explicitlyworkspace-ignore-specific- Ignore specific workspaces when neededworkspace-isolate-for-strict- Isolate workspaces for strict dependency checkingworkspace-list-cross-deps- List cross-workspace dependencies explicitlyworkspace-per-workspace-plugins- Configure plugins per workspaceworkspace-use-workspace-globs- Use workspace globs for consistent configuration
4. Dependency Analysis (HIGH)
deps-add-unlisted-deps- Add unlisted dependencies to package.jsondeps-avoid-transitive-reliance- Avoid relying on transitive dependenciesdeps-configure-plugin-deps- Configure plugins for tool-specific dependenciesdeps-fix-files-first- Fix unused files before dependenciesdeps-ignore-conditional-deps- Ignore conditionally loaded dependenciesdeps-remove-obsolete-types- Remove obsolete type definition packages
5. Export Detection (MEDIUM-HIGH)
exports-check-class-members- Check class members for unused codeexports-enable-entry-exports- Enable entry export checking for private packagesexports-handle-reexports- Handle re-exports in barrel filesexports-ignore-same-file- Ignore exports used in same fileexports-tag-public-api- Tag public API exports with JSDocexports-trace-usage- Trace export usage before removalexports-use-include-libs- Use include libs for type-based consumption
6. CI Integration (MEDIUM)
ci-add-to-pipeline- Add Knip to CI pipelineci-separate-production-check- Separate production and default mode checksci-use-cache- Enable cache for faster CI runsci-use-max-issues- Use max issues for gradual adoptionci-use-reporters- Use appropriate reporters for CI outputci-watch-mode-local- Use watch mode for local development
7. Auto-Fix Workflow (MEDIUM)
fix-allow-remove-files- Explicitly allow file removalfix-format-after-fix- Format code after auto-fixfix-review-before-commit- Review auto-fix changes before commitfix-update-deps-after- Update package manager after dependency fixfix-use-fix-type- Use fix type for targeted cleanup
8. Performance Optimization (LOW-MEDIUM)
perf-filter-issue-types- Filter issue types for focused analysisperf-limit-output- Limit output for large codebasesperf-profile-performance- Profile performance for slow analysisperf-use-bun-runtime- Use Bun runtime for faster analysisperf-use-cache-flag- Enable cache for repeated analysisperf-use-workspace-filter- Filter workspaces for faster monorepo analysis
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
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 |
FAQ
What does the knip-deadcode skill do?
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.json, dead code, unused exports, unused dependencies, bundle optimization.
How do I install knip-deadcode?
Run npx skills add https://github.com/pproenca/dot-skills --skill knip-deadcode in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/knip-deadcode/ (personal) or .claude/skills/knip-deadcode/ (project).
Which AI agents can use knip-deadcode?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is knip-deadcode safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains knip-deadcode?
It is published by pproenca in pproenca/dot-skills. It has 381 recorded installs.
More from pproenca/dot-skills
zod
pproenca/dot-skills
Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).
vitest
pproenca/dot-skills
Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
react-hook-form
pproenca/dot-skills
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, the subscribe() API, and the Watch / FormStateSubscribe / FieldArray render-prop components. Covers RHF 7.82 additions including resetDefaultValues() and the disabled field-array option. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).
emilkowal-animations
pproenca/dot-skills
Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.
nuqs
pproenca/dot-skills
nuqs (type-safe URL query state) best practices for Next.js and other React frameworks. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, limitUrlUpdates, Standard Schema, NuqsAdapter, or Next.js routing with state.
clean-architecture
pproenca/dot-skills
Clean Architecture principles and best practices from Robert C. Martin's book. This skill should be used when designing software systems, reviewing code structure, or refactoring applications to achieve better separation of concerns. Triggers on tasks involving layers, boundaries, dependency direction, entities, use cases, or system architecture.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.