← ClaudeAtlas

handle-codebase-scanlisted

Inspects and fixes cubic codebase scan findings through MCP. Use when the user asks to show, investigate, or fix codebase scan issues; provides a cubic scan CSV; or names a scan issue UUID.
mrge-io/skills · ★ 2 · Data & Documents · score 54
Install: claude install-skill mrge-io/skills
# Handle Codebase Scan Retrieve full scan reports through cubic MCP, verify each finding against the current checkout, and make only the changes the user requests. ## Instructions ### 1. Choose the input path - For a repository request, detect `owner/repo` from `git remote get-url origin`. Support common HTTPS and SSH GitHub URLs and remove a trailing `.git`. - If the repository cannot be identified, call `list_scans` to discover accessible repositories. Do not call it first when the current repository is known. - For a CSV request, read the supplied local CSV and extract valid UUIDs from the `violationId` query parameter in its `Issue link` column. Deduplicate the UUIDs and ignore the scan ID portion of each URL because `get_issue` uses the stable issue UUID. ### 2. Retrieve findings - In repository mode, call `get_scan` with `owner`, `repo`, `triageStatus: "open"`, `limit: 10`, and `offset: 0` by default. The response aggregates the latest completed full scan with newer completed diff scans; it does not accept a scan ID. - Apply `category`, `minSeverity`, `filePath`, or a different `triageStatus` only when the user asks for it. For "unresolved" findings, retrieve both `open` and `in_review`. Retrieve all statuses only when the user explicitly asks for them. - Do not follow `hasMore` by default. Show the first page and its total count, then fetch another page only when the user asks for more or explicitly requested a larger result set. - For listing r