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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
Reference these guidelines when:
| 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- |
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 analysisentry-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 modeworkspace-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 configurationdeps-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 packagesexports-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 consumptionci-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 developmentfix-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 cleanupperf-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 analysisRead individual reference files for detailed explanations and code examples:
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
The English summary is being prepared. Showing the original description.
A scoring scale for evaluating how well a CLI is designed for AI agents, based on the "Rewrite Your CLI for AI Agents" principles.
The English summary is being prepared. Showing the original description.
Score a repository's agentic legibility from repo-visible evidence only. Use when Codex needs to audit how easy a codebase is for coding agents to discover, bootstrap, validate, and navigate, especially for harness-engineering reviews, developer-experience audits, repo cleanup, or before/after comparisons after improving docs, tooling, or architectural constraints.
The English summary is being prepared. Showing the original description.
Expert in Astro framework with static generation and partial hydration patterns
The English summary is being prepared. Showing the original description.
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
The English summary is being prepared. Showing the original description.
Adopt better-result in an existing TypeScript codebase. Use when replacing try/catch, Promise rejection handling, null sentinels, or thrown domain exceptions with typed Result workflows.
The English summary is being prepared. Showing the original description.