# Sc4sap:release

> CTS Transport Release workflow — list, validate, release, and confirm import

- **Type:** Skill
- **Install:** `agentstack add skill-babamba2-superclaude-for-sap-release`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [babamba2](https://agentstack.voostack.com/s/babamba2)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [babamba2](https://github.com/babamba2)
- **Source:** https://github.com/babamba2/superclaude-for-sap/tree/main/skills/release

## Install

```sh
agentstack add skill-babamba2-superclaude-for-sap-release
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# SC4SAP Release

Full CTS (Change and Transport System) transport release workflow. Hybrid mode: confirms transport selection interactively, then auto-executes validation and release steps.

sc4sap:release guides you through the complete CTS transport release process: listing available transports, selecting the target, validating pre-release conditions, performing the release, and confirming import readiness. It prevents releasing transports with syntax errors or inactive objects.

Every response triggered by this skill MUST begin with `[Model:  · Dispatched: ]` per [`../../common/model-routing-rule.md`](../../common/model-routing-rule.md) § Response Prefix Convention.

- User says "release", "release transport", "release CTS", "push to QAS", or "transport release"
- A development cycle is complete and objects need to move to the next system (QAS/PRD)
- User wants to validate a transport before releasing
- User wants to check what is in a transport before releasing

- User wants to create a new transport -- use `/sc4sap:create-object` (which handles transport assignment) or `CreateTransport` directly
- User wants to import a transport (import is done on the target system by Basis)
- Task is not transport-related

**Confirm** (interactive): Transport selection — always asks the user to confirm which transport to release.
**Auto-execute**: Validation and release steps run automatically after confirmation.

This ensures you never accidentally release the wrong transport, but don't need to manually trigger each validation step.

**Step 1 - List Transports** (auto)
- Call `ListTransports` to retrieve open modifiable transports
- Display table: Transport No | Description | Owner | Object Count | Last Changed
- Highlight transports owned by current user

**Step 2 - Select Transport** (confirm required)
- Present list and ask: "Which transport do you want to release? (Enter transport number)"
- User confirms transport number
- Call `GetTransport` to show full transport details including object list

**Step 3 - Pre-Release Validation** (auto, after confirmation)
- **Syntax check**: For each ABAP object in transport, verify via `GetAbapAST` or `GetAbapSemanticAnalysis` — abort if any syntax errors
- **Inactive objects check**: Call `GetInactiveObjects` — abort if any objects in the transport are still inactive
- **Object completeness**: Verify all referenced objects (used classes, interfaces) are either in this transport or already in the target system
- Display validation report: PASS / FAIL per check

**Step 4 - Release** (auto, only if Step 3 all PASS)
- If any validation failed: display errors and stop — do NOT release
- If all validations pass: proceed with transport release
- Report release result: transport number, release timestamp, status

**Step 5 - Import Confirmation**
- Display post-release summary:
  - Transport number and description
  - Released at timestamp
  - Object count
  - Target system(s) in transport route
- Reminder: "Transport released. Import on target system must be triggered by Basis or via STMS."
- Optionally display next steps for the target system import queue

- Syntax errors found: list each object with error message; do not release; suggest fix via direct MCP `Update*` calls or re-run `/sc4sap:create-program`
- Inactive objects found: list each inactive object; do not release; suggest activation
- Transport already released: report status and skip release step
- Authorization error on release: report S_TRANSPRT authorization requirement

- `ListTransports` — retrieve open transports
- `GetTransport` — transport details and object list
- `GetAbapAST` — syntax validation per object
- `GetAbapSemanticAnalysis` — semantic validation
- `GetInactiveObjects` — check for inactive objects

Task: {{ARGUMENTS}}

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [babamba2](https://github.com/babamba2)
- **Source:** [babamba2/superclaude-for-sap](https://github.com/babamba2/superclaude-for-sap)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-babamba2-superclaude-for-sap-release
- Seller: https://agentstack.voostack.com/s/babamba2
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.