refactor-clean

To remove dead Salesforce code safely, detect unreferenced Apex classes and orphaned LWC components using Salesforce Code Analyzer or PMD output, classify findings by safety taxonomy, and delete items one at a time with Apex test runs and dry-run deployments after each change.

The safest workflow for PMD remediation classifies findings into SAFE, CAUTION, and DANGER categories, removes one item at a time, checks metadata references and Flow usage, runs Apex tests, performs dry-run deployments, and keeps checkpoints for safe reversion.

Yes, you can consolidate duplicate Apex implementations by extracting shared logic into utility or service classes, updating all callers to reference the new centralized code, and validating the consolidation with the full Apex test suite.

Salesforce Code Analyzer or PMD output is preferred for automated detection of unused methods and orphaned LWC components, but manual repository heuristics can be used as a fallback when static analysis tools are not available.

Before deleting unreferenced Apex classes, check for metadata references in Flows and Process Builders, managed-package exposures, and annotations like @AuraEnabled and @InvocableMethod that may indicate hidden runtime dependencies.

You should clean up dead Salesforce code before an AppExchange security review to reduce technical debt, remove commented-out or legacy code, and remediate high-severity static analysis findings that could otherwise delay the approval process.