abap-cds-model-check
CommandOptional intended usage such as analytical, transactional, reuse, value-help, or extraction
Optional target version or version range to evaluate
$ npx -y skills add secondsky/sap-skills --agent claude-code
name: sap-dependency-upgrade-plan
description: Create a safe SAP dependency upgrade plan with pinning, changelog review, lockfile checks, and rollback steps
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "[package-or-ecosystem] [target-version]"
arguments:
- name: package_or_ecosystem
description: Optional package, MCP server, npm/pip ecosystem, or plugin dependency area to plan
required: false
- name: target_version
description: Optional target version or version range to evaluate
required: falseCreate a dependency upgrade plan. Do not update files unless the user explicitly asks for implementation.
1. Inventory package manifests, lockfiles, MCP configs, plugin manifests, and runtime version constraints. 2. Flag unpinned specs, `@latest`, bare executable package names, deprecated packages, and security-sensitive config. 3. Check changelogs or package metadata when network access is available. 4. Plan upgrades in small batches with test commands and rollback steps. 5. Separate safe local updates from changes requiring SAP tenant/runtime validation.
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.
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 API style lens such as REST, OData, OpenAPI, or SDK
Optional scenario lens such as extension, integration, analytics, or AI
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.