review-api-usage

# Review API Usage Check API, library, and framework usage in code against official documentation and installed skill knowledge. Return structured findings. ## Step 1: Determine the Scope Determine what to review: - If a specific **diff command** was provided (e.g., `git diff --cached`, `git diff main...HEAD`), use that. - If a **file list or directory** was provided, review those files directly (read the full files, not a diff). - If **neither** was provided, default to diffing against the repository's default branch (detect via `gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'`). ## Step 2: Extract Library Usage 1. For diff scope: run the diff command to obtain the changes and identify external library/framework APIs in changed lines. For file scope: read the specified files and identify all external library/framework API usage. 2. Cross-reference with project dependency files to determine library versions in use 3. Filter out standard library and language built-ins. Focus on third-party dependencies. If no external library usage is found, report that and stop. ## Step 3: Look Up Documentation For each identified library with non-trivial usage in the diff: 1. Resolve the library using documentation MCP tools or WebSearch 2. Query for the specific APIs, methods, or configuration patterns being used 3. Note the documented signatures, parameter types, return types, deprecation status, and version requirements Prioritize libraries where the diff int...