ide-quality

# IDE Quality Sweep Workflow ## Prerequisites 1. Check if the `getToolCapabilities` MCP tool is available to you. - **Available**: call it, check `extensionConnected` → use **IDE Path** below. - **Not available**: use **CLI Path** below. ## IDE Path Use this path when bridge MCP tools are available and extension is connected. ### Phase 1: Assess the environment 1. Use `getToolCapabilities` to discover available linters, formatters, and test runners 2. Use `getProjectInfo` to understand the project type and languages 3. Determine the scope: if `$ARGUMENTS` is provided, focus on that path; otherwise sweep the whole workspace ### Phase 2: Collect all diagnostics 4. Use `getDiagnostics` to get errors and warnings across the workspace 5. Group diagnostics by severity (error → warning → info) and by file 6. Report the total count: "Found N errors, M warnings across K files" ### Phase 3: Auto-fix 7. For each file with fixable diagnostics: - Use `fixAllLintErrors` to apply auto-fixes - Use `organizeImports` to clean up imports - Use `formatDocument` to apply consistent formatting 8. Use `getDiagnostics` again to see what remains after auto-fixing 9. Report: "Auto-fixed X issues. Y issues remain that need manual attention." ### Phase 4: Manual fixes (remaining errors only) 10. For remaining errors (not warnings), analyze the diagnostic message 11. Use `getHover` and `goToDefinition` to understand the context 12. Use `editText` to apply targeted fixes 13. Use...