abap-workflow

星标0

分支1

更新时间2026年6月16日 17:16

Standard ABAP object workflow (discover, create or edit, check, activate, validate).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

abapify

abapify/adt-bench

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

abap-workflow

The canonical sequence for working with any ABAP object via the ADT REST API:

Discover — call /sap/bc/adt/discovery (or your server's equivalent) to learn which endpoints are available. The MCP tools should expose this for you; use them.
Search — before creating, search for the object name. Avoid creating duplicates.
Create (if needed) — POST to the create endpoint with the appropriate descriptor (e.g. application/vnd.sap.adt.oo.classes.v2+xml for a class). The response includes a Location header with the new URI.
Lock — POST ?_action=LOCK&accessMode=MODIFY to acquire an edit lock. Save the LOCK_HANDLE from the response body.
Write source — PUT the source to the include URI with the lock handle. Content-Type: text/plain; charset=utf-8.
Unlock — POST ?_action=UNLOCK&lockHandle=... to release.
Activate — POST to /sap/bc/adt/activation with the object references.
Validate — read the source back, run a syntax check, or run ABAP Unit if applicable.

The CSRF token dance: a GET request with X-CSRF-Token: Fetch returns a token in the response header. Pass the same token (and the cookies) on every state-changing request.

同仓库更多 Skills

同仓库

agent-task

abapify/adt-bench

How to consume a GitHub issue body as an agent task prompt. The 9-section template, the lifecycle, the failure modes.

2026-06-160

principles

abapify/adt-bench

The 12 design principles this codebase is built on. Read first, before any task.

2026-06-160

sdd

abapify/adt-bench

Spec-driven development — the practice of writing the spec before the code. With the 9-section template and the three pnpm spec-check gates.

2026-06-160

abap-mock-usage

abapify/adt-bench

Differences and deterministic behavior of the mock ADT server used by adt-bench smoke runs.

2026-06-160

abap-result-contract

abapify/adt-bench

How to return a strict scenario result JSON with evidence and no extra prose.

2026-06-160

abap-test-loop

abapify/adt-bench

Test-driven loop for ABAP — inspect, change, check syntax, run unit tests, diagnose, fix.

2026-06-160

name	abap-workflow
description	Standard ABAP object workflow (discover, create or edit, check, activate, validate).

abap-workflow

The canonical sequence for working with any ABAP object via the ADT REST API:

Discover — call /sap/bc/adt/discovery (or your server's equivalent) to learn which endpoints are available. The MCP tools should expose this for you; use them.
Search — before creating, search for the object name. Avoid creating duplicates.
Create (if needed) — POST to the create endpoint with the appropriate descriptor (e.g. application/vnd.sap.adt.oo.classes.v2+xml for a class). The response includes a Location header with the new URI.
Lock — POST ?_action=LOCK&accessMode=MODIFY to acquire an edit lock. Save the LOCK_HANDLE from the response body.
Write source — PUT the source to the include URI with the lock handle. Content-Type: text/plain; charset=utf-8.
Unlock — POST ?_action=UNLOCK&lockHandle=... to release.
Activate — POST to /sap/bc/adt/activation with the object references.
Validate — read the source back, run a syntax check, or run ABAP Unit if applicable.

The CSRF token dance: a GET request with X-CSRF-Token: Fetch returns a token in the response header. Pass the same token (and the cookies) on every state-changing request.