nexus-slop-killer

Yes, static analysis for Nexus apps checks for unused imports, orphan exports, ghost components, and dead types. It generates structured reports with file paths, line numbers, and confidence scores to help you safely remove dead code and stale comments.

Audit mode identifies dead code and related slop by scanning TypeScript source files without making changes. It reports unused imports, orphan exports, ghost components, dead types, and stale comments with categorized outputs including file paths and confidence scores.

Yes, clean mode performs safe removals of orphan exports and ghost components in TypeScript files. For more aggressive cleanup, deep mode requires explicit confirmation before removing dead code, ensuring you maintain control over structural changes.

Yes, loading nexus-core first is a required safety constraint before running dead code detection. This ensures accurate static analysis and safe removals by providing the necessary project context for identifying unused imports, dead types, and ghost components.

Deep mode requires explicit confirmation before executing because it performs more aggressive dead code and slop removal than audit or clean modes. This safety constraint prevents unintended changes to TypeScript source files during comprehensive code cleanup operations.

Using clean mode provides safe automated removal of stale comments and dead types across TypeScript files. For comprehensive cleanup, deep mode requires confirmation but thoroughly removes all detected slop, generating structured reports with file paths and confidence scores.