菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/pproenca/dot-skills --skill knip-deadcode命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | knip-deadcode |
| description | 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. |
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 |
Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.
Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.
Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.