Menu
Create a session summary file in docs/sessions/ before merging a PR. Captures date, PR number, title, and concise summary of work done.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run ATC syntax check on the SAP system to detect syntax errors after git pull.
Trigger an abapGit repository pull on the SAP system to sync the current codebase.
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.
| name | session-summary |
| description | Create a session summary file in docs/sessions/ before merging a PR. Captures date, PR number, title, and concise summary of work done. |
Create a session summary file before merging the PR. The summary must be committed to the feature branch.
docs/sessions/YYYY-MM-DD_PR-NN_short-title.md
PR-32). Use no-pr if no PR was created.Examples:
2026-05-21_PR-32_consolidate-duplicate-messages.md2026-05-20_PR-19_refactor-customlogic-resolver.md2026-05-21_no-pr_http-context-and-input-validation.md# YYYY-MM-DD PR-NN short-title
**Date:** YYYY-MM-DD
**Title:** Short descriptive title
## Summary
One paragraph. Include: what was done, key changes, artifacts created/modified, test results, PR number. Keep concise but complete enough to reconstruct context later.