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.
Install
npx skills add pproenca/dot-skills --skill knip-deadcodegit clone --depth 1 https://github.com/pproenca/dot-skills.git /tmp/dot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/dot-skills/skills/.experimental/knip-deadcode ~/.claude/skills/knip-deadcodePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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`](references/config-avoid-broad-ignore.md) - Avoid broad ignore patterns - [`config-configure-path-aliases`](references/config-configure-path-aliases.md) - Configure path aliases in Knip
Details
- Skill name
knip-deadcode- Repository
- pproenca/dot-skills
- Path
skills/.experimental/knip-deadcode/SKILL.md- License
- MIT
- Repo updated
- 15 August 2026
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 the Knip Deadcode skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pproenca/dot-skills --skill knip-deadcode. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Knip Deadcode popular?
It lives in pproenca/dot-skills, which has 228 GitHub stars and 19 forks.
Related skills
12 Factor App
228pproenca/dot-skills
The Twelve-Factor App methodology for building scalable, maintainable cloud-native applications. Use when designing backend services, APIs, microservices, or any software-as-a-service application. Triggers on deployment patterns, configuration management, process architecture, logging, and infrastructure decisions.
37signals Rails
228pproenca/dot-skills
37signals Rails coding principles and conventions from DHH, Jorge Manrubia, and the Fizzy/Basecamp/HEY codebase. This skill should be used when writing, reviewing, or refactoring Ruby on Rails code following the 37signals philosophy — vanilla Rails, CRUD controllers, rich domain models, concerns, no service objects, Hotwire, Turbo, Stimulus, Solid Queue, Solid Cache, Solid Cable, multi-tenancy, Minitest, custom auth, or DHH conventions.
Acceptance Pipeline Catalog
228pproenca/dot-skills
Use when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing. Covers parser, JSON IR, generator, runtime, step handlers, test runner, mutator, value mutation rules, execution, result classification, reporting, project layout, conformance, and agent setup. Based on Uncle Bob's Acceptance Pipeline Specification. Trigger even when the user mentions Gherkin parsing, acceptance test generation, mutation testing for acceptance tests, or building a portable test pipeline.
Language Evolution
191jwynia/agent-skills
Design evolving language systems for fictional worlds. Use when creating language families, dialects, linguistic history, or when language should reflect cultural and historical development.
Keep It Simple
201swyxio/skills
Review a diff, design, execution path, or subsystem for unnecessary complexity and propose concrete simplifications. Use during code review or independently when the user is concerned about overengineering, excessive coordination, or code that has become hard to understand or operate.
Library Reference Distillation
228pproenca/dot-skills
Methodology for starting a new library-reference distillation skill — one that turns an external library (nuqs, zod, framer-motion, msw, react-hook-form, emilkowal-animations) into an idiomatic-usage rule pack — or evolving one against a new upstream release. Distills the conventions empirically shared across shipped library-ref skills in this repo — the source-priority ladder (docs → blog/changelog → issues → types → examples), version pinning that inverts with API velocity, the universal 4-tier category ladder (CRITICAL setup → HIGH isolation → MEDIUM composition → LOW edge cases), the 4-slo
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.