review-function-visibility

To find unused public functions for refactoring, run the query_visibility.ps1 script to audit function visibility boundaries and identify public functions that lack external callers. The audit analyzes caller counts to suggest candidates that should be renamed to private.

Function visibility auditing is the process of analyzing codebases to identify misclassified public or private functions. You need it during code maintenance and refactoring efforts to ensure private functions are correctly marked and public functions are intentionally exposed.

Yes, you can analyze external caller counts using the provided PowerShell scripts. The tooling verifies function usage and impact by providing detailed information about where functions are called from before you make any visibility changes.

The best way to clean up misclassified public functions is to audit function visibility boundaries using the query_visibility.ps1 script. It identifies hundreds of mistakenly marked public functions that are only used internally and provides tools to verify impact before renaming.

Yes, the function visibility auditing tool works without external dependencies. It relies on included scripts and references to analyze your codebase and identify misclassified public or private functions for cleanup.