find-dead-code | SkillBundle

Find Dead Code

Detect unused code that can be safely removed.

Report findings, do not delete. Removal is a separate task.
Focus on production code (ols/). Skip tests unless explicitly asked.
Vulture has false positives — classify each finding before recommending removal.
Code used only via dynamic dispatch (e.g. Pydantic validators, FastAPI dependencies) is not dead.

Ask the user:

For branch mode:

git diff --name-only origin/main -- 'ols/' | grep '\.py$'

uvx vulture <target> --min-confidence 80

--min-confidence 80 reduces noise. Lower confidence findings are more likely false positives.

uv run pylint --disable=all --enable=unused-import,unused-variable,unused-argument,unreachable

Cross-reference with vulture findings to increase confidence.

Common false positives in this codebase:

Pattern	Why it's not dead
Pydantic `model_validator`, `field_validator`	Called by Pydantic, not directly
FastAPI dependency functions	Injected via `Depends()`
`__eq__`, `__hash__`, `__str__`	Called implicitly by Python
Constants used in config YAML	Referenced by config loader
Abstract method implementations	Called via base class interface
Imports re-exported from `__init__.py`	Used by external consumers

For each finding, classify:

Category	Criteria	Action
Remove	Clearly unused, no dynamic references	Safe to delete
Verify	Possibly used dynamically or externally	Search for string references before removing
False positive	Pydantic/FastAPI/magic method	Skip

For "Verify" findings, search for string-based references:

For each finding:

Summary: total findings, how many safe to remove, estimated lines saved.