review-tool-coverage

You can audit query tools for accuracy by verifying they correctly parse current code formats, detecting outdated parsing logic, and flagging scripts that produce incorrect outputs for refactoring.

The best way to identify missing query tools is to scan the codebase for patterns indicating manual large-file analysis, which flags coverage gaps and recommends integrating new query tools to handle those files.

You can find unused query tools by running a code audit that cross-references tools referenced in skills and documentation against actual usage, flagging irrelevant tools as retirement candidates to reduce maintenance overhead.

Use a query tool coverage audit before a major refactor to verify existing tools correctly support the new code structure and to identify any new query tools needed to analyze the changes.

Yes, you can integrate niche query tools into existing skills to improve their capabilities, which enhances analysis functions without increasing per-session context or requiring standalone tool maintenance.

The limitations of auditing query tools include focusing specifically on PowerShell scripts and query tools in the tools directory, meaning it may not detect coverage gaps or accuracy issues in unsupported script languages or external utilities.