plugin-audit

To audit Vercel-plugin performance, you can use an automated tool that analyzes Claude Code conversation logs, extracts tool calls, matches hook inputs, and checks cache staleness to generate a structured report of performance metrics and gaps.

A plugin performance audit analyzes Claude Code conversation logs to extract tool calls, match hook inputs against those calls, identify coverage gaps, and validate plugin cache staleness against the latest version.

Yes, you need Claude Code project logs and an existing Vercel-plugin setup, as the audit process relies on parsing these conversation logs to extract tool usage data and identify performance coverage gaps.

You identify Vercel-plugin coverage gaps by matching hook inputs against extracted tool calls within conversation logs, which highlights mismatched patterns and uncovers missing tool usage in your project.

You check Vercel-plugin cache staleness by validating the existing plugin cache against the latest version, allowing the audit process to detect and report outdated cache entries that may impact performance.

The best way to automate tool usage analysis is running an audit skill that parses Claude Code logs, extracts tool calls, and automatically generates a structured report of performance metrics and plugin coverage gaps.