# Cap Change Workflow

> Use for end-to-end CAP change workflows: modify CDS/handlers, regenerate artifacts, and run a short verification checklist for this repository.

- Skill: `sap-samples/cap-change-workflow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sap-samples/cap-change-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sap-samples/cap-change-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: sap-samples (https://skillmd.com/u/sap-samples)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sap-samples/cap-change-workflow

---


# CAP Change Workflow

Use this skill when implementing non-trivial CAP changes (CDS, services, handlers, annotations) and you want a consistent implementation + verification flow.

## When to use

- Adding/changing entities, associations, projections, or service exposure
- Updating `cap/srv/*.js` handlers or event hooks
- Regenerating build artifacts and validating basic runtime behavior

## Procedure

1. Clarify requested behavior and impacted files.
2. If CDS is involved:
   - Resolve definitions with cds-mcp first.
   - Check CAP docs with cds-mcp before proposing CAP API/CLI syntax.
3. Implement minimal changes in appropriate layer:
   - `cap/db` for domain model
   - `cap/srv/*-service.cds` for contracts
   - `cap/srv/*-fiori.cds` for UI annotations
   - `cap/srv/*.js` for runtime logic
4. Rebuild artifacts in `cap/` (`npm run build`) when CDS changed.
5. Run a compact verification checklist and report outcomes.
6. Document risks, assumptions, and follow-ups.

## Repository gotchas

- After HANA deployment, generated folders can be cleared; run `npm run build` again.
- SQLite local loading may hit `SQLITE_BUSY` with parallel loading.

## Checklist template

Use this checklist after implementation: `assets/change-checklist.md`.