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.

Ir para a instalação

Repositório: pproenca/dot-skills
Última atividade na origem: 27 de maio de 2026 às 09:50
Idioma detectado do SKILL.md: inglês
Estrelas: 194
Forks: 17

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/pproenca/dot-skills --skill knip-deadcode

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

55 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

drizzle-nextjs-postgres

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.

2026-07-24

relational-data-modeling

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.

2026-07-23

relational-database-design

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.

2026-07-23

Ver todas deste repositório

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.

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 patterns
config-configure-path-aliases - Configure path aliases in Knip
config-enable-plugins-explicitly - Enable framework plugins explicitly
config-run-without-config - Run without config first for baseline
config-separate-entry-project - Separate entry files from project files
config-use-json-schema - Use JSON schema for configuration validation
config-use-negation-patterns - Use negation patterns for exclusions
config-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 points
entry-exclude-test-files - Exclude test files from production entries
entry-include-all-entry-points - Include all application entry points
entry-include-bin-scripts - Include binary scripts as entry points
entry-use-compilers - Use compilers for non-standard file types
entry-use-plugin-entries - Use plugin entry points for frameworks
entry-verify-with-debug - Verify entry points with debug mode

3. Workspace & Monorepo (HIGH)

workspace-configure-root-workspace - Configure root workspace explicitly
workspace-ignore-specific - Ignore specific workspaces when needed
workspace-isolate-for-strict - Isolate workspaces for strict dependency checking
workspace-list-cross-deps - List cross-workspace dependencies explicitly
workspace-per-workspace-plugins - Configure plugins per workspace
workspace-use-workspace-globs - Use workspace globs for consistent configuration

4. Dependency Analysis (HIGH)

deps-add-unlisted-deps - Add unlisted dependencies to package.json
deps-avoid-transitive-reliance - Avoid relying on transitive dependencies
deps-configure-plugin-deps - Configure plugins for tool-specific dependencies
deps-fix-files-first - Fix unused files before dependencies
deps-ignore-conditional-deps - Ignore conditionally loaded dependencies
deps-remove-obsolete-types - Remove obsolete type definition packages

5. Export Detection (MEDIUM-HIGH)

exports-check-class-members - Check class members for unused code
exports-enable-entry-exports - Enable entry export checking for private packages
exports-handle-reexports - Handle re-exports in barrel files
exports-ignore-same-file - Ignore exports used in same file
exports-tag-public-api - Tag public API exports with JSDoc
exports-trace-usage - Trace export usage before removal
exports-use-include-libs - Use include libs for type-based consumption

6. CI Integration (MEDIUM)

ci-add-to-pipeline - Add Knip to CI pipeline
ci-separate-production-check - Separate production and default mode checks
ci-use-cache - Enable cache for faster CI runs
ci-use-max-issues - Use max issues for gradual adoption
ci-use-reporters - Use appropriate reporters for CI output
ci-watch-mode-local - Use watch mode for local development

7. Auto-Fix Workflow (MEDIUM)

fix-allow-remove-files - Explicitly allow file removal
fix-format-after-fix - Format code after auto-fix
fix-review-before-commit - Review auto-fix changes before commit
fix-update-deps-after - Update package manager after dependency fix
fix-use-fix-type - Use fix type for targeted cleanup

8. Performance Optimization (LOW-MEDIUM)

perf-filter-issue-types - Filter issue types for focused analysis
perf-limit-output - Limit output for large codebases
perf-profile-performance - Profile performance for slow analysis
perf-use-bun-runtime - Use Bun runtime for faster analysis
perf-use-cache-flag - Enable cache for repeated analysis
perf-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

knip-deadcode

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Community Knip Dead Code Detection Best Practices

When to Apply

Rule Categories by Priority

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

Reference Files

Community Knip Dead Code Detection Best Practices

When to Apply

Rule Categories by Priority

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

Reference Files