shift: Skill for Claude Code

/dead-code — Find and Remove Dead Code

Use this skill to find unused files, exports, and class members in the codebase. It uses Knip as a candidate generator, then verifies each candidate through AST-level analysis and interface tracing before removing anything.

NEVER use knip --fix — it has previously deleted code that was actually in use, breaking the editor and tests.

Phase 1: Discovery

Run Knip to generate candidates:

pnpm deadcode 2>&1        # unused files + exports
pnpm deadcode:class 2>&1  # unused class members

Parse the output into three categories:

• Unused files — files with zero imports
• Unused exports — exported symbols with no consumers
• Unused class members — class methods/properties reported as unused

Phase 2: Verification

For each candidate, apply the appropriate checks below. Use scripts/find-refs.ts when reading code alone is insufficient.

Verifying Unused Files

1. Grep for the filename (without extension) across the codebase
2. Check config references: tsconfig.json, vite.*.config.ts, forge.config.ts
3. Check if it's a test helper imported by test files (Knip may miss test-only imports)
4. Check if it's referenced in package.json scripts or CI workflows

Verifying Unused Exports

1. Check if re-exported by a barrel file (index.ts) consumed by another package
2. Check if used in extends/implements clauses
3. Check if used only in test files (Knip sometimes misses test imports)
4. Run npx tsx scripts/find-refs.ts <file> <symbol> for compiler-level reference count

Verifying Unused Class Members (Main Pain Point)

This is where most false positives occur. Knip cannot trace usage through interfaces, composite types, or dep interfaces.

Check these patterns in order:

1. Interface contract — Is the member defined on an interface the class implements? Check the known interface contracts below.
2. Composite type — Is the class consumed through a type intersection? e.g., ShiftEditor = EditorAPI & CanvasCoordinatorContext means all EditorAPI members on Editor are used.
3. Dep interface — Is the member part of a dependency injection interface? Classes implement dep interfaces that are consumed by managers.
4. Base class — Is the member defined on a base class (BaseCommand, BaseTool) and used by subclasses?
5. Abstract member — Is it an abstract method that subclasses must implement?
6. Find References — Run npx tsx scripts/find-refs.ts <file> <memberName> for compiler confirmation.