← ClaudeAtlas

clean-core-checklisted

Check an ABAP object or package for clean core compliance — unreleased APIs, direct SELECT on SAP-owned tables, classic constructs disallowed in ABAP Cloud, modifications to SAP standard. Use when the user asks to audit, verify, or check clean core compliance, ABAP Cloud compatibility, released API usage, or extension point usage. Produces a categorised report with hard violations and soft warnings. Read-only — never writes back. Targets BTP ABAP Environment and S/4HANA on-prem in the ABAP Cloud development model.
matt1as/claude-abap-skills · ★ 9 · AI & Automation · score 77
Install: claude install-skill matt1as/claude-abap-skills
# abap-cloud-rap:clean-core-check Check an ABAP object or package for clean core compliance. Pulls the source via the SAP ABAP MCP Server and produces a categorised compliance report with concrete remediation steps. ## What this command does You are auditing one or more ABAP objects for compliance with the **clean core** principles enforced by ABAP Cloud development model. The rules in `../CLAUDE.md` define what is allowed; this command finds what is not. Output is a structured report — **read-only**, no writes back via MCP. ## Inputs If not provided, ask. Defaults to the narrowest scope. - An ABAP object name (class, function group, program, include, CDS entity, BDEF) - A package name - A transport request — check every object in the transport ## What to check For each object in scope, look for the following. Each maps to a rule in `CLAUDE.md`. ### Hard violations — never allowed in either BTP or S/4HANA on-prem Cloud development | Check | Source rule | |------------------------------------------------------|------------------------------------------| | Use of an SAP class/interface/FM with no C1 release | `released-apis-only` | | Direct `SELECT` from a SAP-owned database table | `no-direct-select-on-sap-owned-tables` | | Classic dynpro (`CALL SCREEN`, screen exits) | `abap-cloud-language-scope-only` | | `SUBMIT`, `CALL TRANSACTION`, `LEAVE TO`