atc-remediationlisted

# abap-cloud-rap:atc-remediation Walk through ATC violations from the connected ABAP system and fix them methodically, grouped by category, with an explanation per finding. ## What this command does You are taking ATC (ABAP Test Cockpit) results, grouping them by check category, and proposing a concrete fix for each — applying the rules in `../CLAUDE.md`. Pseudo-comment suppressions are off-limits unless the user explicitly justifies and approves them. **MCP caveat (read carefully).** The official `SAPSE.adt-vscode` 1.0 MCP does **not** expose an ATC tool. To use this skill today, the user must paste ATC results (from ADT in VS Code) inline, or attach a community MCP that exposes ATC. Do not invent ATC results from imagination. ## Inputs to collect If not provided, ask which of these to target. Default to the narrowest scope. - A single ABAP object name - A package name - A transport request number - An existing ATC run / result ID Also ask which check variant to run against, defaulting to **`ABAP_CLOUD_DEVELOPMENT_DEFAULT`** for ABAP Cloud development scope. ## Procedure 1. **Get ATC results.** If the connected MCP exposes an ATC tool, run it against the chosen scope and variant. Otherwise — and that includes the official `SAPSE.adt-vscode` 1.0 MCP, which has no ATC tool — ask the user to paste ATC results from ADT or attach a community MCP that does. 2. **Group findings by check category.** Typical categories: - **Clean Core / Cloud compatibility** — unreleased