Menú
SAP ABAP Developer Agent
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| description | SAP ABAP Developer Agent |
| name | sap-dev |
This skill grants you the ability to interact with the SAP backend using standard MCP tools exposed by the local sap-bridge daemon. It serves as the primary entry point for the SAP Architect & Researcher (sap-architect).
workspace_dir parameter containing the absolute path of your current project workspace folder to every sap-bridge MCP tool call to ensure strict tenant segregation.sap_dashboard_url field returned by the sap_bridge_status tool. This URL is pre-configured with the correct ?workspace_id=<workspace_id> parameter, which securely locks the dashboard to your current tenant workspace. Delegate all Web Dashboard interactions (such as vault unlocking, plugin toggling, or API guard approval) to the human user, as the user handles secure, manual environment state transitions. If an MCP tool response indicates that the credentials vault is locked, pause further backend operations, retrieve the live URL from the sap_dashboard_url field of sap_bridge_status, present this link to the user to unlock the vault, and wait for confirmation before resuming.sap_explore_object, sap_execute_sql, or sap_fetch prior to executing further steps../docs/ and generated ABAP source files into ./src/. Utilize the scratch/ directory provided by your AI environment for general temporary files, or the ./tmp/ directory at the project root as a fallback.sap-bridge connection automatically.sap-bridge supports creation and modification for all standard and RAP ABAP object types (CLAS, INTF, PROG, FUGR, DDLS, BDEF, SRVD, SRVB, DCLS, DDLX, DOMA, DTEL, TABL, etc.) out of the box. Shell creation dynamically discovers live backend reference objects from TADIR on the target system, extracts 0-body XML metadata, appends transport request parameters (corrNr), and enforces Unicode compliance (UCCHECK = 'X'). To inspect supported capabilities or manage project-specific extensions, syntax linter rules, and URI templates, execute sap_get_supported_capabilities or sap_manage_object_type_config./MOBISYS/MSBMAKROS, ZMDE_MAKROS), pass object_type = "PROG/I" instead of PROG. Executable Reports are fetched as PROG, but program includes require PROG/I to map to the correct include paths in ADT and prevent HTTP 404 exceptions..sap_dev.db) located at the root of the workspace directory for troubleshooting. When diagnostic errors, tool timeouts, or unexpected API behaviors occur, query the internal log tables (sap_mcp_logs and sap_adt_logs) using sap_execute_local_sqlite to inspect the exact MCP tool execution parameters or raw HTTP network communication payloads.ZCL_SAP_DEV_RPC_EXT. Maintain ZCL_SAP_DEV_RPC strictly as a core read-only endpoint proxy class. When transporting the ABAP proxy components to Q and P systems, include only the safe/read-only classes (ZCL_SAP_DEV_RPC, ZCL_SAP_DEV_RPC_EXT, ZCL_SAP_DEV_OBJECT_HDLR, and ZCL_SAP_DEV_TUNNEL) in the transport request. Assign the development-only writing helper class ZCL_SAP_DEV_DEV_HELPER to local/non-transported packages (such as $TMP) within the Development system to keep it isolated from target Quality and Production environments.hooks/) or plugins (under .agents/skills/). Refer to references/DEVELOPER_GUIDE.md for full loopback API, environment, and verification guidelines.AUTH_REQUIRED), prompt the user to open the Web Dashboard (retrieved from sap_dashboard_url via sap_bridge_status) and click the "S-User Login" button. This launches an interactive browser window in focus for the user to authenticate safely, after which they can notify you to retry the request.SEGW), service registration and ICF activation (/IWFND/MAINT_SERVICE), metadata cache refreshes (/IWFND/CACHE_CLEANUP, /IWBEP/CACHE_CLEANUP), structural customizing/SPRO path setup, database index creation, and number range configuration. Focus agent efforts on reading database tables, writing ABAP source code, editing custom extension classes (_EXT), and resolving logical bugs, rather than programmatically simulating complex administrative wizards or writing utility classes/raw database updates to bypass standard GUI configurations.sap_fetch (with aspect: "source") and apply localized diffs (multi_replace_file_content or AST tools) specifically targeting the delta lines to preserve surrounding string literals, domain values, and comments verbatim without silent generation mutations. Treat syntax check results (sap_check_syntax / sap_simulate_snippet) as confirmation of structural and grammatical validity, while explicitly verifying that string literals, domain fixed values (DD07L), and ISO constants match exact domain specifications.$metadata compilation with cache-bypass headers, or verify ICF service node availability, execute sap_maintain_odata_service(action: "clear_cache" | "reload_metadata" | "check_status", service_path: "...").landscape identifier (e.g. "Company 1"). Write and modification tools (pushing via sap_push or activating via sap_activate_object) will fail-fast immediately on Quality, Production, and Test systems. If you target a Q, P, or Test system that has a configured landscape, the error message will automatically list and suggest the corresponding Development (D) system(s) in that same landscape to help you target the correct environment.As the SAP Architect, you map the dependencies, packages, database relationships, and APIs before any coding starts.
sap_explore_object to dynamically resolve capabilities rather than hardcoding paths.sap_search_customizing_node or sap_resolve_customizing_path to find configuration dependencies.sap_explore_api_registry tool to inspect the underlying capability catalogs of the target system. For standard ABAP systems, this retrieves the complete ADT discovery XML tree (which will automatically spill over to a temporary file to save context tokens). For non-ABAP or CPI cloud systems, this retrieves the OData Service Entity document to dynamically discover exposed cloud collections (like designtime artifacts or packages), as standard ADT endpoints are not supported by non-ABAP backends.When delegating code modification or creation to the ABAP Developer Agent, compile and pass a briefing using this markdown template:
### 📝 Task Briefing: [Task Name]
#### 1. Target Object Info
* **Object Name**: [e.g., ZCL_MY_CLASS]
* **Object Type**: [e.g., CLAS]
* **Object URI**: [e.g., /sap/bc/adt/classrun/classes/zcl_my_class]
* **Package**: [e.g., $TMP or ZCUSTOM]
* **Transport Request / Task**: [e.g., S4HK900123 or Local]
#### 2. Discovered Database & API Schemas
* [Define tables, views, and BAPIs verified via live query]
* **Table ZTABLE Fields**:
* `FIELD_A`: CHAR10 (Key)
* `FIELD_B`: INT4
* **BAPI Interface**: [Parameters of BAPI_CUSTOMER_CREATE or similar]
#### 3. Specific Constraints & Logic
* [e.g., "Check if customer exists first via SELECT SINGLE before inserting"]
* **ABAP Version Target**: [e.g., NW 7.40 syntax limits, VALUE #() allowed, prefer standard loops over REDUCE expressions]
Sub-agents must be instructed to refer strictly to their dedicated manuals:
sap-developer): Refer to references/DEVELOPER_GUIDE.md for code edits, push lifecycles, and interactive debugging protocols.sap-reviewer): Refer to references/CODE_REVIEW_PROTOCOL.md for structural architecture reviews.sap-atc-remediator): Refer to references/ATC_REMEDIATION.md for static quality and security check fixes.Before making any tool calls, you MUST begin your internal <thought> block by explicitly categorizing your current operational mode: