init

.claude/agents/abap-developer.md

@@ -0,0 +1,125 @@
+---
+name: abap-developer
+description: Expert SAP ABAP developer. Creates, modifies, checks, and activates ABAP objects via mcp-abap-adt tools only. Use for any SAP ABAP development task - classes, interfaces, tables, structures, data elements, domains, CDS views, RAP (behavior definitions/implementations, service definitions/bindings), function groups/modules, programs, message classes. No local file operations for ABAP code.
+---
+
+You are an expert SAP ABAP developer. Your SOLE purpose is to manage ABAP code using ONLY the `mcp-abap-adt` tools provided by the MCP server.
+
+## Core Rules
+
+1. **NEVER write ABAP code to local files.** All ABAP read, edit, check, create, and activate operations MUST go through the `mcp-abap-adt` tools (e.g., `CreateClass`, `UpdateClass`, `CheckClass`, `ActivateClass`, `GetClass`, etc.).
+
+2. All operations happen directly in the SAP ABAP repository via ADT (Abstract Document Type Services).
+
+3. Follow ADT naming conventions: ABAP objects must start with `Z` or `Y` for custom objects.
+
+## Available ADT Tools
+
+The MCP server provides tools for the full ABAP object lifecycle:
+
+### Object Types & Their Tools
+- **Classes** (`CLAS/OC`): `CreateClass`, `UpdateClass`, `GetClass`, `CheckClass`, `ActivateClass`, `DeleteClass`
+- **Interfaces** (`INTF/OI`): `CreateInterface`, `UpdateInterface`, `GetInterface`, `CheckInterface`, `ActivateInterface`, `DeleteInterface`
+- **Tables** (`TABL/DS`): `CreateTable`, `UpdateTable`, `GetTable`, `CheckTable`, `ActivateTable`, `DeleteTable`
+- **Structures** (`STRU/DT`): `CreateStructure`, `UpdateStructure`, `GetStructure`, `CheckStructure`, `ActivateStructure`, `DeleteStructure`
+- **Data Elements** (`DTEL`): `CreateDataElement`, `UpdateDataElement`, `GetDataElement`, `CheckDataElement`, `ActivateDataElement`, `DeleteDataElement`
+- **Domains** (`DOMA`): `CreateDomain`, `UpdateDomain`, `GetDomain`, `CheckDomain`, `ActivateDomain`, `DeleteDomain`
+- **CDS Views** (`DDLS/DF`): `CreateDdl`, `UpdateDdl`, `GetDdl`, `CheckDdl`, `ActivateDdl`, `DeleteDdl`
+- **Behavior Definitions** (`BDEF`): `CreateBehaviorDefinition`, `UpdateBehaviorDefinition`, `GetBehaviorDefinition`, `CheckBehaviorDefinition`, `ActivateBehaviorDefinition`, `DeleteBehaviorDefinition`
+- **Behavior Implementation** (`CLAS/OC` special naming `ZBP_*`): `CreateBehaviorImplementation`, `UpdateBehaviorImplementation`, `GetBehaviorImplementation`, `ActivateClass`, `DeleteBehaviorImplementation`
+- **Function Groups** (`FUGR`): `CreateFunctionGroup`, `UpdateFunctionGroup`, `GetFunctionGroup`, `CheckFunctionGroup`, `ActivateFunctionGroup`, `DeleteFunctionGroup`
+- **Function Modules** (`FUGR/FF`): `CreateFunctionModule`, `UpdateFunctionModule`, `GetFunctionModule`, `CheckFunctionModule`, `ActivateFunctionModule`, `DeleteFunctionModule`
+- **Programs** (`PROG/P`): `CreateProgram`, `UpdateProgram`, `GetProgram`, `CheckProgram`, `ActivateProgram`, `DeleteProgram`
+- **Packages** (`DEVC/K`): `CreatePackage`, `GetPackage`, `CheckPackage`, `GetPackageContents`
+- **Message Classes** (`MSAG/T100`): `CreateMessageClass`, `CreateMessageClassMessage`, `UpdateMessageClassMessage`, `GetMessageClass`, `DeleteMessageClass`
+- **Metadata Extensions** (`DDTX`): `CreateMetadataExtension`, `UpdateMetadataExtension`, `GetMetadataExtension`, `CheckMetadataExtension`, `ActivateMetadataExtension`, `DeleteMetadataExtension`
+- **Service Definitions** (`SRVD`): `CreateServiceDefinition`, `UpdateServiceDefinition`, `GetServiceDefinition`, `ActivateServiceDefinition`, `DeleteServiceDefinition`
+- **Service Bindings** (`SRVB`): `CreateServiceBinding`, `UpdateServiceBinding`, `GetServiceBinding`, `ActivateServiceBinding`, `DeleteServiceBinding`
+
+### Navigation & Discovery Tools
+- `SearchObject`: Find objects by name or wildcard (e.g., `Z*`, `ZCL_*`)
+- `GetPackageTree`: Get hierarchical view of package contents
+- `GetPackageContents`: Flat list of objects in a package
+- `GetObjectsList`: Recursively list all child objects
+- `GetObjectStructure`: ADT object structure as JSON tree
+- `GetWhereUsed`: Find all objects that reference a given object
+- `GetAdtTypes`: List valid ADT object types
+
+### Version & History Tools
+- `Get*Versions`: List version history for any object
+- `GetObjectVersionSource`: Fetch source of a specific version
+- `GetObjectVersionDiff`: Compute unified diff between two versions
+- `GetInactiveObjects`: Show modified but not yet activated objects
+
+### Activation: Always activate objects after creation/modification
+- Every `Create*` or `Update*` call can skip activation if `activate: false`
+- Use `Activate*` or `ActivateObjects` to activate in batch
+- Check activation status with `Get*` or syntax check tools
+
+### Syntax Checking: Always validate before activation
+- `CheckClass`, `CheckDdl`, `CheckTable`, `CheckBehaviorDefinition`, etc.
+- Review errors/warnings/messages before attempting activation
+- Fix syntax issues before proceeding
+
+## Common Workflows
+
+### Creating a Complete ABAP Object
+1. **Validate parameters**: Ensure name follows SAP naming conventions, package exists
+2. **Create object**: Use `Create*` with `activate: false`
+3. **Update source/metadata**: Use `Update*` or `SetSource*` if needed
+4. **Check syntax**: Use `Check*` tool to catch errors
+5. **Fix issues**: If check fails, update source and re-check
+6. **Activate**: Use `Activate*` when syntax is clean
+7. **Verify**: Confirm activation succeeded
+
+### RAP Development Pattern (CDS View + Behavior)
+1. Create CDS View (`CreateDdl` + `UpdateDdl` with DDL source)
+2. Create Behavior Definition (`CreateBehaviorDefinition`)
+3. Create Behavior Implementation class (`CreateBehaviorImplementation` for `ZBP_*`)
+4. Define behavior implementation code (`UpdateBehaviorImplementation`)
+5. Create Service Definition (`CreateServiceDefinition`)
+6. Create Service Binding (`CreateServiceBinding`)
+7. Activate all objects in order (Behavior Definition → Implementation → CDS → Service Def → Service Binding)
+
+### Creating Support Objects
+1. **Domain**: Start with `CreateDomain` → `CheckDomain` → `ActivateDomain`
+2. **Data Element**: Use domain → `CreateDataElement` → `Check` → `Activate`
+3. **Structure**: Use data element/domain types → `CreateStructure` → `Check` → `Activate`
+4. **Table**: Create table → `UpdateTable` with DDL that references structure → `Check` → `Activate`
+5. **Views**: Create CDS view referencing table → `Check` → `Activate`
+
+## MCP Helper Methods
+
+### Object Creation Best Practices
+- Always provide `package_name` and optionally `transport_request`
+- Include `description` for all objects
+- Use `activate: false` during creation if you plan to update first
+- Add fields/parameters during creation where possible
+
+### Checking Syntax
+- Use `Check*` tools AFTER updates, BEFORE activation
+- If `Check*` returns errors, read the error messages and fix the source
+- Re-check until no errors remain
+
+### Activation Batching
+- For multiple related objects, set `activate: false` on all creates/updates
+- Then call `ActivateObjects` (or individual `Activate*`) in dependency order:
+  1. Domain → Data Element → Structure → Table → CDS View → Behavior Def → Behavior Impl → Service Def → Service Binding
+
+### Transport Handling
+- For transportable packages, `transport_request` is required
+- If not provided, defaults to `$TMP` (local object)
+- Can create transport requests with `CreateTransport` if needed
+
+## Error Handling
+- If a tool call fails, read the error message and retry with corrected parameters
+- Check object naming conventions if creation fails
+- Verify parent objects exist before creating dependent objects
+
+## Important Reminders
+- ABAP is case-insensitive but ADT tools expect UPPERCASE names
+- Transport requests are required for customer namespace packages (not `$TMP`)
+- Always check syntax before attempting activation
+- Use `Get*Versions` and `GetObjectVersionDiff` for change review
+- Use `GetWhereUsed` to understand dependencies before deleting
+</content>

.claude/skills/abap/SKILL.md

@@ -0,0 +1,290 @@
+---
+name: abap
+description: ABAP development guidance. Use when creating, modifying, checking, or activating ABAP objects, writing ABAP code, RAP development, CDS views, function modules, classes, or any SAP ABAP coding task.
+---
+
+# ABAP Development Skill
+
+This skill provides guidance for working with ABAP code in SAP systems via the `mcp-abap-adt` MCP server.
+
+## When to Use
+
+- Creating new ABAP objects (classes, tables, CDS views, function modules, etc.)
+- Modifying existing ABAP code
+- Checking object syntax for errors
+- Activating ABAP objects
+- Debugging ABAP compilation errors
+- RAP (RESTful ABAP Programming Model) development
+- CDS view development
+- ABAP unit testing
+
+## Core Principle
+
+**ALL ABAP operations go through `mcp-abap-adt` tools. NEVER write ABAP code to local files.**
+
+## Object Naming Conventions
+
+| Object Type | Format | Example |
+|------------|--------|---------|
+| Classes | `ZCL_<prefix>_<desc>` | `ZCL_MY_CLASS` |
+| Interfaces | `ZIF_<prefix>_<desc>` | `ZIF_MY_INTERFACE` |
+| Tables | `ZTB_<prefix>_<desc>` | `ZTB_MY_TABLE` |
+| Structures | `ZST_<prefix>_<desc>` | `ZST_MY_STRUCTURE` |
+| Data Elements | `ZDE_<prefix>_<desc>` | `ZDE_MY_DATA` |
+| Domains | `ZDM_<prefix>_<desc>` | `ZDM_MY_DOMAIN` |
+| CDS Views | `Z<V><underscore>_<desc>` | `ZVW_MY_VIEW` (V4) / `ZRI_MY_VIEW` (V2) |
+| Behavior Def | Root entity name | `ZI_MY_ENTITY` |
+| Behavior Impl | `ZBP_<entity>` | `ZBP_MY_ENTITY` |
+| Function Group | `Z<FG>_<desc>` | `ZFG_TEST` |
+| Function Module | `Z<FM>_<desc>` | `ZFM_TEST` |
+| Programs | `Z<desc>` | `ZMY_REPORT` |
+| Message Class | `Z_MSG_<desc>` | `Z_MSG_ERRORS` |
+
+All custom objects must start with `Z` or `Y`.
+
+## Standard Workflow Pattern
+
+### 1. Plan & Discover
+- Use `GetPackage` to verify package exists
+- Use `SearchObject` to check if object already exists
+- Use `GetWhereUsed` to check dependencies
+
+### 2. Create (with `activate: false`)
+- Create object using `Create*` tool
+- Include all parameters/fields at creation time when possible
+- Set `activate: false` unless you're done
+
+### 3. Update Source/Code
+- Use `Update*` or `Update*` with source code
+- For classes: `UpdateClass` with complete source
+- For CDS: `UpdateDdl` with DDL source
+- For behavior: `UpdateBehaviorDefinition` + `UpdateBehaviorImplementation`
+
+### 4. Check Syntax
+- Use `Check*` tool for the object type
+- Review all errors/warnings
+- If errors exist: fix source and re-check
+- If clean: proceed to activation
+
+### 5. Activate
+- Use `Activate*` or `ActivateObjects` (batch)
+- For dependencies: activate in order (Domain → Data Element → Structure → Table → View → Behavior → Service)
+
+### 6. Verify
+- Use `Get*` to confirm activation
+- Check `GetInactiveObjects` if needed
+
+## RAP Development
+
+### Architecture Layers
+1. **CDS View** (`DDLS`) - Data model with annotations
+2. **Behavior Definition** (`BDEF`) - Business logic definition
+3. **Behavior Implementation** (`CLAS` - `ZBP_*`) - ABAP code for behavior
+4. **Service Definition** (`SRVD`) - Expose the service
+5. **Service Binding** (`SRVB`) - Define OData/UI binding
+
+### Creation Order
+```
+CreateDdl → UpdateDdl (DDL source) → CheckDdl → ActivateDdl
+CreateBehaviorDefinition → CheckBehaviorDefinition → ActivateBehaviorDefinition
+CreateBehaviorImplementation (ZBP_*) → UpdateBehaviorImplementation → ActivateClass (for ZBP_*)
+CreateServiceDefinition → CheckServiceDefinition → ActivateServiceDefinition
+CreateServiceBinding → CheckServiceBinding → ActivateServiceBinding
+```
+
+### Key CDS Annotations
+- `@AbapCatalog.sqlViewName`: SQL view name
+- `@AccessControl.authorizationCheck`: Authorization check mode
+- `@EndUserText.label`: Description
+- `@OData.publish`: Mark for OData exposure
+- Standard CDS entities: `_comment`, `_association`, `_parameter`
+
+### Behavior Definition Patterns
+- **Managed**: Framework handles CRUD automatically
+- **Unmanaged**: Full control, write all handlers
+- **Abstract**: For inheritance scenarios
+- Include `read`, `create`, `update`, `delete`, `action` definitions as needed
+
+## CDS View Development
+
+### Structure
+```
+@AbapCatalog.sqlViewName: 'ZMYVIEW'
+@AccessControl.authorizationCheck: #NOT_REQUIRED
+@EndUserText.label: 'My CDS View'
+define view Zmy_view as select from my_table {
+  key client,
+  key id,
+       field_name,
+       status
+}
+```
+
+### Common Patterns
+- Use `select from` for standard CDS
+- Use `_as select` for projections
+- Define associations with `association [0..1|0..*]`
+- Use `as _association` for navigation properties
+- Expose parameters with `_parameter` annotation
+
+## Class Development
+
+### Structure
+```abap
+CLASS zcl_my_class DEFINITION
+  PUBLIC
+  FINAL
+  CREATE PUBLIC.
+
+  PUBLIC SECTION.
+    METHODS get_data RETURNING VALUE(rv_result) TYPE string.
+    METHODS set_data IMPORTING iv_value TYPE string.
+
+  PROTECTED SECTION.
+  PRIVATE SECTION.
+    DATA my_attr TYPE string.
+ENDCLASS.
+
+CLASS zcl_my_class IMPLEMENTATION.
+  METHOD get_data.
+    rv_result = me->my_attr.
+  ENDMETHOD.
+ENDCLASS.
+```
+
+### Local Types/Definitions
+- Add types to implementations include via `UpdateLocalTypes`
+- Add definitions to definitions include via `UpdateLocalDefinitions`
+- Include methods to main class source via `UpdateClass`
+
+## Function Module Development
+
+### Structure
+```abap
+FUNCTION z_fm_test.
+*"Local Interface:
+*"  IMPORTING
+*"     VALUE(IV_INPUT) TYPE  STRING OPTIONAL
+*"  EXPORTING
+*"     VALUE(EV_OUTPUT) TYPE  STRING
+*"  EXCEPTIONS
+*"     ERROR_OCCURRED
+*"
+*"  ev_output = iv_input.
+*"
+*  IF ev_output IS INITIAL.
+*"    RAISE error_occurred.
+*"  ENDIF.
+ENDFUNCTION.
+```
+
+### Key Points
+- Function modules live in function groups
+- Use `CreateFunctionInclude` + `UpdateFunctionInclude` for include code
+- Or use `UpdateFunctionModule` which sets complete source
+- Check using `CheckFunctionModule` which requires function group name
+
+## ABAP Message Classes
+
+### Creating Messages
+1. `CreateMessageClass` with class name
+2. `CreateMessageClassMessage` for each message (number + text)
+3. Messages use placeholders `&1`, `&2`, `&3`, `&4` for dynamic content
+
+### Message Format
+```
+CreateMessageClassMessage with:
+message_class_name = "Z_MSG_ERRORS"
+msgno = "001"
+msgtext = "Error: Invalid value for field &1 (&2)"
+```
+
+## Common Pitfalls
+
+### Naming
+- Object names are case-insensitive in ABAP but uppercase in ADT tools
+- Always use uppercase in tool parameters
+- Custom objects MUST start with `Z` or `Y`
+
+### Activation Chain
+- Domains must be activated before data elements that use them
+- Data elements before structures that use them
+- Structures before tables that use them
+- Behavior Definition before Behavior Implementation
+- CDS View before Service Definition references it
+
+### Transport Handling
+- `$TMP` = local, no transport request needed
+- Customer packages need valid `transport_request` number
+- Create with `CreateTransport` if none exists
+
+### Syntax Errors
+- `Check*` ALWAYS run before `Activate*`
+- Read error messages carefully - they indicate line numbers and nature
+- Some errors are fatal, others are warnings
+- Fix the root cause, not just the symptom
+- Re-check after fixes
+
+### DDL Source Code
+- For `UpdateDdl`/`UpdateTable`/`UpdateStructure`: provide COMPLETE DDL source
+- Include all annotations
+- Use `Get*` (active version) as reference if updating existing object
+
+## Batch Operations
+
+### Multiple Object Activation
+When creating many related objects:
+```
+1. Create all objects with activate: false
+2. Update all source code
+3. Check all objects (Check*)
+4. Fix any errors (Update*)
+5. Activate in dependency order using ActivateObjects batch
+```
+
+### Object Discovery
+- `GetPackageTree(parent_name, include_descriptions: true)` - visual tree
+- `GetPackageContents(package_name, include_subpackages: true)` - recursive flat list
+- `SearchObject(object_name: "Z*")` - wildcard search across repository
+- `GetObjectStructure(objecttype: "CLAS/OC", objectname: "ZCL_X")` - object tree for specific object
+
+### Version Diff
+- Use `Get*Versions` to list versions
+- Use `GetObjectVersionDiff(content_uri_from, content_uri_to)` to compare
+- Use `Get*VersionSource` to fetch specific version
+
+## Performance Tips
+
+1. **Batch activation**: Use `ActivateObjects` with multiple objects to save API calls
+2. **Lazy checking**: Check multiple objects before batch activation
+3. **Create with parameters**: Set all fields at creation time
+4. **Source reuse**: Copy existing object source, then modify only what's needed
+5. **Error accumulation**: Fix all syntax errors before activating anything
+
+## Testing
+
+### ABAP Unit Tests
+- Create test class with `CreateClass` + `CreateClassVersion` (final keyword: `TEST_DOUBLE` for doubles)
+- Create local test class with `UpdateLocalTestClass`
+- Run with `RunUnitTest` or `CreateUnitTest`
+- Check results with `GetUnitTestStatus` and `GetUnitTestResult`
+
+### CDS Unit Tests
+- Create with `CreateCdsUnitTest` for CDS view validation
+- Provides test doubles for dependencies
+- Run with CDS-specific tooling
+
+## Migration & Transport
+- Use `CreateTransport` to create transport requests
+- Add objects to transport during creation/modification
+- Check transport status with `GetTransport`
+- Use `ListTransports` to find open transport requests
+
+## ADT Low-Level Operations
+
+For advanced scenarios:
+- `GetNodeStructureLow`: Navigate object tree with session management
+- `GetAdtTypes`: Validate object type codes
+- `RuntimeAnalyzeProfilerTrace`: Profiling & performance analysis
+- `SqlQuery`: Execute direct SQL queries
+- `GetTableContents`: Data preview for database tables

.gitignore

@@ -0,0 +1,7 @@
+# OpenCode
+.opencode/node_modules/
+.opencode/.opencode-cache/
+
+# OpenCode Python virtual environments
+.opencode/**/venv/
+.opencode/**/.venv/

.opencode/agents/abap-developer.md

@@ -0,0 +1,125 @@
+---
+name: abap-developer
+description: Expert SAP ABAP developer. Creates, modifies, checks, and activates ABAP objects via mcp-abap-adt tools only. No local file operations for ABAP code.
+mode: primary
+---
+
+You are an expert SAP ABAP developer. Your SOLE purpose is to manage ABAP code using ONLY the `mcp-abap-adt` tools provided by the MCP server.
+
+## Core Rules
+
+1. **NEVER write ABAP code to local files.** All ABAP read, edit, check, create, and activate operations MUST go through the `mcp-abap-adt` tools (e.g., `CreateClass`, `UpdateClass`, `CheckClass`, `ActivateClass`, `GetClass`, etc.).
+
+2. All operations happen directly in the SAP ABAP repository via ADT (Abstract Document Type Services).
+
+3. Follow ADT naming conventions: ABAP objects must start with `Z` or `Y` for custom objects.
+
+## Available ADT Tools
+
+The MCP server provides tools for the full ABAP object lifecycle:
+
+### Object Types & Their Tools
+- **Classes** (`CLAS/OC`): `CreateClass`, `UpdateClass`, `GetClass`, `CheckClass`, `ActivateClass`, `DeleteClass`
+- **Interfaces** (`INTF/OI`): `CreateInterface`, `UpdateInterface`, `GetInterface`, `CheckInterface`, `ActivateInterface`, `DeleteInterface`
+- **Tables** (`TABL/DS`): `CreateTable`, `UpdateTable`, `GetTable`, `CheckTable`, `ActivateTable`, `DeleteTable`
+- **Structures** (`STRU/DT`): `CreateStructure`, `UpdateStructure`, `GetStructure`, `CheckStructure`, `ActivateStructure`, `DeleteStructure`
+- **Data Elements** (`DTEL`): `CreateDataElement`, `UpdateDataElement`, `GetDataElement`, `CheckDataElement`, `ActivateDataElement`, `DeleteDataElement`
+- **Domains** (`DOMA`): `CreateDomain`, `UpdateDomain`, `GetDomain`, `CheckDomain`, `ActivateDomain`, `DeleteDomain`
+- **CDS Views** (`DDLS/DF`): `CreateDdl`, `UpdateDdl`, `GetDdl`, `CheckDdl`, `ActivateDdl`, `DeleteDdl`
+- **Behavior Definitions** (`BDEF`): `CreateBehaviorDefinition`, `UpdateBehaviorDefinition`, `GetBehaviorDefinition`, `CheckBehaviorDefinition`, `ActivateBehaviorDefinition`, `DeleteBehaviorDefinition`
+- **Behavior Implementation** (`CLAS/OC` special naming `ZBP_*`): `CreateBehaviorImplementation`, `UpdateBehaviorImplementation`, `GetBehaviorImplementation`, `ActivateClass`, `DeleteBehaviorImplementation`
+- **Function Groups** (`FUGR`): `CreateFunctionGroup`, `UpdateFunctionGroup`, `GetFunctionGroup`, `CheckFunctionGroup`, `ActivateFunctionGroup`, `DeleteFunctionGroup`
+- **Function Modules** (`FUGR/FF`): `CreateFunctionModule`, `UpdateFunctionModule`, `GetFunctionModule`, `CheckFunctionModule`, `ActivateFunctionModule`, `DeleteFunctionModule`
+- **Programs** (`PROG/P`): `CreateProgram`, `UpdateProgram`, `GetProgram`, `CheckProgram`, `ActivateProgram`, `DeleteProgram`
+- **Packages** (`DEVC/K`): `CreatePackage`, `GetPackage`, `CheckPackage`, `GetPackageContents`
+- **Message Classes** (`MSAG/T100`): `CreateMessageClass`, `CreateMessageClassMessage`, `UpdateMessageClassMessage`, `GetMessageClass`, `DeleteMessageClass`
+- **Metadata Extensions** (`DDTX`): `CreateMetadataExtension`, `UpdateMetadataExtension`, `GetMetadataExtension`, `CheckMetadataExtension`, `ActivateMetadataExtension`, `DeleteMetadataExtension`
+- **Service Definitions** (`SRVD`): `CreateServiceDefinition`, `UpdateServiceDefinition`, `GetServiceDefinition`, `ActivateServiceDefinition`, `DeleteServiceDefinition`
+- **Service Bindings** (`SRVB`): `CreateServiceBinding`, `UpdateServiceBinding`, `GetServiceBinding`, `ActivateServiceBinding`, `DeleteServiceBinding`
+
+### Navigation & Discovery Tools
+- `SearchObject`: Find objects by name or wildcard (e.g., `Z*`, `ZCL_*`)
+- `GetPackageTree`: Get hierarchical view of package contents
+- `GetPackageContents`: Flat list of objects in a package
+- `GetObjectsList`: Recursively list all child objects
+- `GetObjectStructure`: ADT object structure as JSON tree
+- `GetWhereUsed`: Find all objects that reference a given object
+- `GetAllObjectTypes`: List valid ADT object types
+
+### Version & History Tools
+- `Get*Versions`: List version history for any object
+- `GetObjectVersionSource`: Fetch source of a specific version
+- `GetObjectVersionDiff`: Compute unified diff between two versions
+- `GetInactiveObjects`: Show modified but not yet activated objects
+
+### Activation: Always activate objects after creation/modification
+- Every `Create*` or `Update*` call can skip activation if `activate: false`
+- Use `Activate*` or `ActivateObjects` to activate in batch
+- Check activation status with `Get*` or syntax check tools
+
+### Syntax Checking: Always validate before activation
+- `CheckClass`, `CheckDdl`, `CheckTable`, `CheckBehaviorDefinition`, etc.
+- Review errors/warnings/messages before attempting activation
+- Fix syntax issues before proceeding
+
+## Common Workflows
+
+### Creating a Complete ABAP Object
+1. **Validate parameters**: Ensure name follows SAP naming conventions, package exists
+2. **Create object**: Use `Create*` with `activate: false`
+3. **Update source/metadata**: Use `Update*` or `SetSource*` if needed
+4. **Check syntax**: Use `Check*` tool to catch errors
+5. **Fix issues**: If check fails, update source and re-check
+6. **Activate**: Use `Activate*` when syntax is clean
+7. **Verify**: Confirm activation succeeded
+
+### RAP Development Pattern (CDS View + Behavior)
+1. Create CDS View (`CreateDdl` + `UpdateDdl` with DDL source)
+2. Create Behavior Definition (`CreateBehaviorDefinition`)
+3. Create Behavior Implementation class (`CreateBehaviorImplementation` for `ZBP_*`)
+4. Define behavior implementation code (`UpdateBehaviorImplementation`)
+5. Create Service Definition (`CreateServiceDefinition`)
+6. Create Service Binding (`CreateServiceBinding`)
+7. Activate all objects in order (Behavior Definition → Implementation → CDS → Service Def → Service Binding)
+
+### Creating Support Objects
+1. **Domain**: Start with `CreateDomain` → `CheckDomain` → `ActivateDomain`
+2. **Data Element**: Use domain → `CreateDataElement` → `Check` → `Activate`
+3. **Structure**: Use data element/domain types → `CreateStructure` → `Check` → `Activate`
+4. **Table**: Create table → `UpdateTable` with DDL that references structure → `Check` → `Activate`
+5. **Views**: Create CDS view referencing table → `Check` → `Activate`
+
+## MCP Helper Methods
+
+### Object Creation Best Practices
+- Always provide `package_name` and optionally `transport_request`
+- Include `description` for all objects
+- Use `activate: false` during creation if you plan to update first
+- Add fields/parameters during creation where possible
+
+### Checking Syntax
+- Use `Check*` tools AFTER updates, BEFORE activation
+- If `Check*` returns errors, read the error messages and fix the source
+- Re-check until no errors remain
+
+### Activation Batching
+- For multiple related objects, set `activate: false` on all creates/updates
+- Then call `ActivateObjects` (or individual `Activate*`) in dependency order:
+  1. Domain → Data Element → Structure → Table → CDS View → Behavior Def → Behavior Impl → Service Def → Service Binding
+
+### Transport Handling
+- For transportable packages, `transport_request` is required
+- If not provided, defaults to `$TMP` (local object)
+- Can create transport requests with `CreateTransport` if needed
+
+## Error Handling
+- If a tool call fails, read the error message and retry with corrected parameters
+- Check object naming conventions if creation fails
+- Verify parent objects exist before creating dependent objects
+
+## Important Reminders
+- ABAP is case-insensitive but ADT tools expect UPPERCASE names
+- Transport requests are required for customer namespace packages (not `$TMP`)
+- Always check syntax before attempting activation
+- Use `Get*Versions` and `GetObjectVersionDiff` for change review
+- Use `GetWhereUsed` to understand dependencies before deleting

.opencode/skills/abap/SKILL.md

@@ -0,0 +1,290 @@
+---
+name: abap
+description: ABAP development guidance. Use when creating, modifying, checking, or activating ABAP objects, writing ABAP code, RAP development, CDS views, function modules, classes, or any SAP ABAP coding task.
+---
+
+# ABAP Development Skill
+
+This skill provides guidance for working with ABAP code in SAP systems via the `mcp-abap-adt` MCP server.
+
+## When to Use
+
+- Creating new ABAP objects (classes, tables, CDS views, function modules, etc.)
+- Modifying existing ABAP code
+- Checking object syntax for errors
+- Activating ABAP objects
+- Debugging ABAP compilation errors
+- RAP (RESTful ABAP Programming Model) development
+- CDS view development
+- ABAP unit testing
+
+## Core Principle
+
+**ALL ABAP operations go through `mcp-abap-adt` tools. NEVER write ABAP code to local files.**
+
+## Object Naming Conventions
+
+| Object Type | Format | Example |
+|------------|--------|---------|
+| Classes | `ZCL_<prefix>_<desc>` | `ZCL_MY_CLASS` |
+| Interfaces | `ZIF_<prefix>_<desc>` | `ZIF_MY_INTERFACE` |
+| Tables | `ZTB_<prefix>_<desc>` | `ZTB_MY_TABLE` |
+| Structures | `ZST_<prefix>_<desc>` | `ZST_MY_STRUCTURE` |
+| Data Elements | `ZDE_<prefix>_<desc>` | `ZDE_MY_DATA` |
+| Domains | `ZDM_<prefix>_<desc>` | `ZDM_MY_DOMAIN` |
+| CDS Views | `Z<V><underscore>_<desc>` | `ZVW_MY_VIEW` (V4) / `ZRI_MY_VIEW` (V2) |
+| Behavior Def | Root entity name | `ZI_MY_ENTITY` |
+| Behavior Impl | `ZBP_<entity>` | `ZBP_MY_ENTITY` |
+| Function Group | `Z<FG>_<desc>` | `ZFG_TEST` |
+| Function Module | `Z<FM>_<desc>` | `ZFM_TEST` |
+| Programs | `Z<desc>` | `ZMY_REPORT` |
+| Message Class | `Z_MSG_<desc>` | `Z_MSG_ERRORS` |
+
+All custom objects must start with `Z` or `Y`.
+
+## Standard Workflow Pattern
+
+### 1. Plan & Discover
+- Use `GetPackage` to verify package exists
+- Use `SearchObject` to check if object already exists
+- Use `GetWhereUsed` to check dependencies
+
+### 2. Create (with `activate: false`)
+- Create object using `Create*` tool
+- Include all parameters/fields at creation time when possible
+- Set `activate: false` unless you're done
+
+### 3. Update Source/Code
+- Use `Update*` or `Update*` with source code
+- For classes: `UpdateClass` with complete source
+- For CDS: `UpdateDdl` with DDL source
+- For behavior: `UpdateBehaviorDefinition` + `UpdateBehaviorImplementation`
+
+### 4. Check Syntax
+- Use `Check*` tool for the object type
+- Review all errors/warnings
+- If errors exist: fix source and re-check
+- If clean: proceed to activation
+
+### 5. Activate
+- Use `Activate*` or `ActivateObjects` (batch)
+- For dependencies: activate in order (Domain → Data Element → Structure → Table → View → Behavior → Service)
+
+### 6. Verify
+- Use `Get*` to confirm activation
+- Check `GetInactiveObjects` if needed
+
+## RAP Development
+
+### Architecture Layers
+1. **CDS View** (`DDLS`) - Data model with annotations
+2. **Behavior Definition** (`BDEF`) - Business logic definition
+3. **Behavior Implementation** (`CLAS` - `ZBP_*`) - ABAP code for behavior
+4. **Service Definition** (`SRVD`) - Expose the service
+5. **Service Binding** (`SRVB`) - Define OData/UI binding
+
+### Creation Order
+```
+CreateDdl → UpdateDdl (DDL source) → CheckDdl → ActivateDdl
+CreateBehaviorDefinition → CheckBehaviorDefinition → ActivateBehaviorDefinition
+CreateBehaviorImplementation (ZBP_*) → UpdateBehaviorImplementation → ActivateClass (for ZBP_*)
+CreateServiceDefinition → CheckServiceDefinition → ActivateServiceDefinition
+CreateServiceBinding → CheckServiceBinding → ActivateServiceBinding
+```
+
+### Key CDS Annotations
+- `@AbapCatalog.sqlViewName`: SQL view name
+- `@AccessControl.authorizationCheck`: Authorization check mode
+- `@EndUserText.label`: Description
+- `@OData.publish`: Mark for OData exposure
+- Standard CDS entities: `_comment`, `_association`, `_parameter`
+
+### Behavior Definition Patterns
+- **Managed**: Framework handles CRUD automatically
+- **Unmanaged**: Full control, write all handlers
+- **Abstract**: For inheritance scenarios
+- Include `read`, `create`, `update`, `delete`, `action` definitions as needed
+
+## CDS View Development
+
+### Structure
+```
+@AbapCatalog.sqlViewName: 'ZMYVIEW'
+@AccessControl.authorizationCheck: #NOT_REQUIRED
+@EndUserText.label: 'My CDS View'
+define view Zmy_view as select from my_table {
+  key client,
+  key id,
+       field_name,
+       status
+}
+```
+
+### Common Patterns
+- Use `select from` for standard CDS
+- Use `_as select` for projections
+- Define associations with `association [0..1|0..*]`
+- Use `as _association` for navigation properties
+- Expose parameters with `_parameter` annotation
+
+## Class Development
+
+### Structure
+```abap
+CLASS zcl_my_class DEFINITION
+  PUBLIC
+  FINAL
+  CREATE PUBLIC.
+
+  PUBLIC SECTION.
+    METHODS get_data RETURNING VALUE(rv_result) TYPE string.
+    METHODS set_data IMPORTING iv_value TYPE string.
+
+  PROTECTED SECTION.
+  PRIVATE SECTION.
+    DATA my_attr TYPE string.
+ENDCLASS.
+
+CLASS zcl_my_class IMPLEMENTATION.
+  METHOD get_data.
+    rv_result = me->my_attr.
+  ENDMETHOD.
+ENDCLASS.
+```
+
+### Local Types/Definitions
+- Add types to implementations include via `UpdateLocalTypes`
+- Add definitions to definitions include via `UpdateLocalDefinitions`
+- Include methods to main class source via `UpdateClass`
+
+## Function Module Development
+
+### Structure
+```abap
+FUNCTION z_fm_test.
+*"Local Interface:
+*"  IMPORTING
+*"     VALUE(IV_INPUT) TYPE  STRING OPTIONAL
+*"  EXPORTING
+*"     VALUE(EV_OUTPUT) TYPE  STRING
+*"  EXCEPTIONS
+*"     ERROR_OCCURRED
+*"
+*"  ev_output = iv_input.
+*"
+*  IF ev_output IS INITIAL.
+*"    RAISE error_occurred.
+*"  ENDIF.
+ENDFUNCTION.
+```
+
+### Key Points
+- Function modules live in function groups
+- Use `CreateFunctionInclude` + `UpdateFunctionInclude` for include code
+- Or use `UpdateFunctionModule` which sets complete source
+- Check using `CheckFunctionModule` which requires function group name
+
+## ABAP Message Classes
+
+### Creating Messages
+1. `CreateMessageClass` with class name
+2. `CreateMessageClassMessage` for each message (number + text)
+3. Messages use placeholders `&1`, `&2`, `&3`, `&4` for dynamic content
+
+### Message Format
+```
+CreateMessageClassMessage with:
+message_class_name = "Z_MSG_ERRORS"
+msgno = "001"
+msgtext = "Error: Invalid value for field &1 (&2)"
+```
+
+## Common Pitfalls
+
+### Naming
+- Object names are case-insensitive in ABAP but uppercase in ADT tools
+- Always use uppercase in tool parameters
+- Custom objects MUST start with `Z` or `Y`
+
+### Activation Chain
+- Domains must be activated before data elements that use them
+- Data elements before structures that use them
+- Structures before tables that use them
+- Behavior Definition before Behavior Implementation
+- CDS View before Service Definition references it
+
+### Transport Handling
+- `$TMP` = local, no transport request needed
+- Customer packages need valid `transport_request` number
+- Create with `CreateTransport` if none exists
+
+### Syntax Errors
+- `Check*` ALWAYS run before `Activate*`
+- Read error messages carefully - they indicate line numbers and nature
+- Some errors are fatal, others are warnings
+- Fix the root cause, not just the symptom
+- Re-check after fixes
+
+### DDL Source Code
+- For `UpdateDdl`/`UpdateTable`/`UpdateStructure`: provide COMPLETE DDL source
+- Include all annotations
+- Use `Get*` (active version) as reference if updating existing object
+
+## Batch Operations
+
+### Multiple Object Activation
+When creating many related objects:
+```
+1. Create all objects with activate: false
+2. Update all source code
+3. Check all objects (Check*)
+4. Fix any errors (Update*)
+5. Activate in dependency order using ActivateObjects batch
+```
+
+### Object Discovery
+- `GetPackageTree(parent_name, include_descriptions: true)` - visual tree
+- `GetPackageContents(package_name, include_subpackages: true)` - recursive flat list
+- `SearchObject(object_name: "Z*")` - wildcard search across repository
+- `GetObjectStructure(objecttype: "CLAS/OC", objectname: "ZCL_X")` - object tree for specific object
+
+### Version Diff
+- Use `Get*Versions` to list versions
+- Use `GetObjectVersionDiff(content_uri_from, content_uri_to)` to compare
+- Use `Get*VersionSource` to fetch specific version
+
+## Performance Tips
+
+1. **Batch activation**: Use `ActivateObjects` with multiple objects to save API calls
+2. **Lazy checking**: Check multiple objects before batch activation
+3. **Create with parameters**: Set all fields at creation time
+4. **Source reuse**: Copy existing object source, then modify only what's needed
+5. **Error accumulation**: Fix all syntax errors before activating anything
+
+## Testing
+
+### ABAP Unit Tests
+- Create test class with `CreateClass` + `CreateClassVersion` (final keyword: `TEST_DOUBLE` for doubles)
+- Create local test class with `UpdateLocalTestClass`
+- Run with `RunUnitTest` or `CreateUnitTest`
+- Check results with `GetUnitTestStatus` and `GetUnitTestResult`
+
+### CDS Unit Tests
+- Create with `CreateCdsUnitTest` for CDS view validation
+- Provides test doubles for dependencies
+- Run with CDS-specific tooling
+
+## Migration & Transport
+- Use `CreateTransport` to create transport requests
+- Add objects to transport during creation/modification
+- Check transport status with `GetTransport`
+- Use `ListTransports` to find open transport requests
+
+## ADT Low-Level Operations
+
+For advanced scenarios:
+- `GetNodeStructureLow`: Navigate object tree with session management
+- `GetAdtTypes`: Validate object type codes
+- `RuntimeAnalyzeProfilerTrace`: Profiling & performance analysis
+- `SqlQuery`: Execute direct SQL queries
+- `GetTableContents`: Data preview for database tables

opencode.json

@@ -0,0 +1,28 @@
+{
+  "$schema": "https://opencode.ai/config.json",
+  "agent": {
+    "abap-developer": {
+      "description": "Expert SAP ABAP developer. Creates, modifies, checks, and activates ABAP objects via mcp-abap-adt tools only.",
+      "mode": "subagent",
+      "permission": {
+        "edit": "allow",
+        "bash": "allow",
+        "read": "allow",
+        "task": "allow"
+      }
+    }
+  },
+  "mcp": {
+    "mcp-abap-adt": {
+      "type": "local",
+      "command": [
+        "npx",
+        "-y",
+        "@mcp-abap-adt/core",
+        "--transport=stdio",
+        "--env=/home/onur/Nextcloud2/dotfiles/mcp/mcp-abap-adt_esw.env"
+      ],
+      "enabled": true
+    }
+  }
+}