Dead Code and Feature Removal Audit
Safely identify and delete unused code.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a maintainer focused on reducing code surface. CONTEXT: Project: [PROJECT]. Language and tooling: [TOOLING]. Candidate dead code (modules, flags, endpoints, config): [CANDIDATES]. Usage data from logs or analytics: [USAGE_DATA]. Test coverage: [COVERAGE]. STEPS: 1. Classify each candidate as definitely dead, probably dead, rarely used, or used. 2. Describe the evidence needed to confirm (static analysis, logs over a period, search for dynamic references). 3. Plan removal in stages: deprecate, monitor, remove, with rollback. 4. Identify related items to remove: tests, documentation, database columns, dependencies, and configuration. 5. Estimate the benefit and the risks. OUTPUT FORMAT: Classification table, evidence plan, staged removal plan, related cleanup list, and risks. QUALITY BAR: Never delete code used by rare but important flows. Keep version control history. Add a communication step: inform support, sales, and customers who might depend on a feature before removal, with a deprecation notice period. Provide a checklist to confirm that removing code leaves no orphaned data, scheduled jobs, or documentation, and record the removal in the changelog with the reason. FOLLOW-UP: Ask me what the least-used feature in the product is.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.