/zombie

Run a dead-code scan to identify unused models, replaced service methods, stale constants, and obsolete migrations. The scan checks for callers and references across six categories, producing a precise list of candidates with contextual guidance for safe removal.

Locate dead migrations and unused cron jobs by scanning the repository for zombie candidates. The scan verifies the existence of targeted tables and features, flagging obsolete artifacts that no longer have active callers or references.

Safely remove unused models and service methods by using an auditable workflow that confirms references and prevents accidental deletion. The scan flags uncertain items for human review, providing justification and contextual guidance before pruning.

Yes, you can identify dead feature branches and stale constants safely. The scan flags uncertain items for human review and provides an auditable workflow to confirm references, preventing accidental deletion of load-bearing code paths.

Use a code-cleanup scan during major refactors, software migrations, or after removing features. It ensures models, services, constants, and cron jobs no longer reference obsolete artifacts, reclaiming a lighter, maintainable codebase.

Dead code clutter weighs down maintenance and slows development by leaving obsolete artifacts in the codebase. Fix it by pruning dead code candidates, which identifies unused paths and provides contextual guidance for safe removal.