From sc4sap
Executes full CTS transport release workflow: lists open modifiable transports, validates ABAP syntax/errors/inactive objects/completeness, releases if valid for QAS/PRD import.
npx claudepluginhub babamba2/superclaude-for-sap --plugin sc4sapThis skill uses the workspace's default tool permissions.
Full CTS (Change and Transport System) transport release workflow. Hybrid mode: confirms transport selection interactively, then auto-executes validation and release steps.
Configures and manages SAP BTP Cloud Transport Management: transport landscapes, nodes/routes, MTA deployments to Cloud Foundry, CI/CD integration, ABAP transports, troubleshooting.
Manages transport packages in SAP Datasphere to move objects between Dev, QA, and Prod tenants. Handles migrations, dependencies, versions, and SAP Content Network imports.
Creates ABAP objects (classes, interfaces, programs, function modules, tables, structures); confirms transport/package, auto-generates code via MCP, activates.
Share bugs, ideas, or general feedback.
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.<Response_Prefix>
Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention.
</Response_Prefix>
<Use_When>
<Do_Not_Use_When>
/sc4sap:create-object (which handles transport assignment) or CreateTransport directly<Hybrid_Mode> 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. </Hybrid_Mode>
<Workflow_Steps>
Step 1 - List Transports (auto)
ListTransports to retrieve open modifiable transportsStep 2 - Select Transport (confirm required)
GetTransport to show full transport details including object listStep 3 - Pre-Release Validation (auto, after confirmation)
GetAbapAST or GetAbapSemanticAnalysis — abort if any syntax errorsGetInactiveObjects — abort if any objects in the transport are still inactiveStep 4 - Release (auto, only if Step 3 all PASS)
Step 5 - Import Confirmation
</Workflow_Steps>
<Error_Handling>
Update* calls or re-run /sc4sap:create-program<MCP_Tools_Used>
ListTransports — retrieve open transportsGetTransport — transport details and object listGetAbapAST — syntax validation per objectGetAbapSemanticAnalysis — semantic validationGetInactiveObjects — check for inactive objects
</MCP_Tools_Used>Task: {{ARGUMENTS}}