القائمة
Trigger an abapGit repository pull on the SAP system to sync the current codebase.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run ATC syntax check on the SAP system to detect syntax errors after git pull.
Run ABAP Unit tests on the remote SAP system via ADT.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
Detailed guidance on which test layer(s) to update and how to write tests for different kinds of changes in the ZASIS project.
Reference guide for the ZASIS exception handling pattern — class hierarchy, message class, T100 integration, how to raise exceptions, and rules for adding new exceptions.
Create a session summary file in docs/sessions/ before merging a PR. Captures date, PR number, title, and concise summary of work done.
| name | adt-gitpull |
| description | Trigger an abapGit repository pull on the SAP system to sync the current codebase. |
Use the built-in adt_gitpull custom tool.
| Parameter | Required | Description |
|---|---|---|
branch | No | Branch to pull (short name like main or full ref like refs/heads/feat/my-feature). If omitted, auto-detects from the currently checked-out git branch. |
checkErrors | No | If true, runs ATC syntax check (variant SYNTAX_CHECK) on the package after pull and appends findings to the output. Default: false. |
.env in the project root (SAP_ADT_URL, SAP_ADT_USER, SAP_ADT_PASSWORD)origin)branch parameter if provided, otherwise detects from git rev-parse --abbrev-ref HEADswitchRepoBranch) if it differs from the currently configured branchrefs/heads/<branch> to the API)Only when the user explicitly requests a sync to SAP. Typical scenarios:
main, user says "sync to SAP" or "pull to SAP"Never call autonomously. Always wait for user trigger.
This tool (and adt_rununit) must only be used in interactive chat mode — never in autonomous/background agent runs. When using in chat mode:
.env in project root with valid credentials (see .env.example):
SAP_ADT_URL=https://your-sap-system:44300
SAP_ADT_USER=DEVELOPER
SAP_ADT_PASSWORD=secret