Fab2295

SAP Cloud Application Programming Model (CAP) development skill for the **Node.js runtime only**. Domain-first: prefers CDS schema, annotations, projections, and CAP's generic providers over hand-written handler code ("less code → less mistakes"). Use when the user asks to: build CAP applications, define CDS models, design entities / associations / views / projections, add annotations (validation,

Upgrade SAP CAP and SAP-related libraries (@sap/cds*, @cap-js/*, @sap-cloud-sdk/*, @sap/eslint-plugin-cds) in the current working directory. Strategy: latest stable including majors. Runs `cds build` + `npm test` (when present), cross-checks failures against locally mirrored official changelogs (CAP + Cloud SDK JS) and reports ONLY bugs caused by the version bump. Use when the user asks to "upgrad

SAP ABAP RESTful Application Programming Model (RAP) development skill. End-to-end scope: business objects (BO), CDS data model, behavior definitions and implementations, service definitions / bindings, file uploads/downloads, metadata extensions, value helps, and RAP testing. Use when the user asks to: build a RAP BO (managed or unmanaged), model CDS view entities / table entities / projection vi

Read-only static analysis of SAP CAP Node.js code (a Pull Request, a branch comparison, or a specific file list). Classifies findings as Critical / High / Medium / Low, lists each finding with file:line, function/class, evidence and a *suggested* fix (always flagged as needing human validation), and writes the result to `CAP-CODE-REVIEW.md` at the project root. Use when the user asks to: - "analis

Test-only skill for SAP CAP Node.js projects. Its sole purpose is to scaffold and run automated tests using `cds test` (Node.js test runner wrapper) and, when (and only when) explicitly requested by the user, produce coverage with `c8`. The skill writes test files under `test/` (or the project's existing test folder), executes them, and emits two possible report files at the project root: - `CAP-T