Core workflows

Inspect code impact and candidates

Use local static analysis to inspect import dependents, sibling-repository edges, and conservative unused-file candidates.

ClaudeKit reads supported local source files and static imports. It makes conservative claims and leaves dynamic behavior, framework routing, generated files, and runtime loading for human review.

Impact analysis

ck impact src/checkout.ts
ck impact src/checkout.ts --depth 5

This refreshes the local code map and reports static import dependents that may need review before changing a source file.

Unused-file candidates

ck dead-code
ck dead-code --json

The detector excludes conventional entry points, package exports, tests, and config files. It reports candidates, not confirmed dead code.

Workspace graph

From a directory containing sibling Git repositories, ClaudeKit can build a local graph of static JavaScript and TypeScript package imports.

cd ~/projects
ck workspace scan .
ck workspace graph .
ck workspace dead-code .

Only static imports that match another sibling package name become workspace edges. A repository imported by another workspace package is skipped from unused-file candidate output to avoid unsafe deletion advice.