abap-cds-model-check
Optional intended usage such as analytical, transactional, reuse, value-help, or extraction
Optional API style lens such as REST, OData, OpenAPI, or SDK
$ npx -y skills add secondsky/sap-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/api-style-reviewContext preview
What this command does when you run it.
Optional API style lens such as REST, OData, OpenAPI, or SDK
name: api-style-review
description: Review SAP API style compliance for REST, OData, OpenAPI, SDK naming, documentation, and lifecycle readiness
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "<api-spec-or-folder> [rest|odata|openapi|sdk]"
arguments:
- name: target
description: API specification file, documentation folder, SDK source folder, or issue summary to review
required: true
- name: api_type
description: Optional API style lens such as REST, OData, OpenAPI, or SDK
required: falseReview API style quality against the SAP API style guidance. Default to read-only inspection; do not rewrite specifications or source files unless separately requested.
1. Identify the API type, target artifact, audience, lifecycle state, and applicable style references. 2. Inspect names, paths, operations, events, parameters, error handling, examples, extensibility, and deprecation metadata. 3. Check documentation completeness, terminology consistency, accessibility of examples, and SDK/API surface alignment. 4. Use `rg` against bundled references for the relevant topic instead of loading large guides wholesale. 5. Separate style defects from product or tenant checks that require owner confirmation.
Return:
40 SAP development plugins with evidence-tracked verification SAP development plugins for AI coding assistants, with public-source or package-registry verification tracked where available.
Repo: secondsky/sap-skills
Optional intended usage such as analytical, transactional, reuse, value-help, or extraction
Optional target ABAP platform or SAP BTP ABAP Environment release
Optional runtime or scenario name, such as orchestration, serving, training, or batch
Optional scenario lens such as extension, integration, analytics, or AI