post-write-chain
Use after ANY WriteSource, EditSource, or Activate operation on SAP ABAP objects. Enforces the mandatory quality gate: SyntaxCheck → RunUnitTests → GetCodeCoverage → RunATCCheck. Trigger automatically after every ABAP write operation.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- post-write-chain
- owner
- test-runner
- scope
- co-abap
- status
- active
- version
- 1.1.0
- metadata
- { "type": "core", "triggers": [ "post-write-chain", "WriteSource", "EditSource", "Activate" ] }
- description
- Use after ANY WriteSource, EditSource, or Activate operation on SAP ABAP objects. Enforces the mandatory quality gate: SyntaxCheck → RunUnitTests → GetCodeCoverage → RunATCCheck. Trigger automatically after every ABAP write operation.
- last_reviewed
- 1786752000000
- prerequisites
- vsp MCP server
03 SKILL.md 正文
⚠️ Desktop App:
PostToolUsehooks do not fire automatically. Run/post-write <object-name>manually after every WriteSource or EditSource in Desktop App sessions.
Post-Write Mandatory Chain
Applies to all tools: Claude Code CLI, Antigravity, Gemini CLI
After ANY WriteSource / EditSource / Activate, the executing agent MUST run these four steps in order:
| Step | Tool | Pass Condition |
|---|---|---|
| 1 | SyntaxCheck |
0 errors |
| 2 | RunUnitTests |
0 failures |
| 3 | GetCodeCoverage |
≥ 70% statement coverage on the changed object (new objects); no regression vs. prior run (existing objects) |
| 4 | RunATCCheck |
0 Priority-1 findings |
ATC Priority Levels
- Priority 1 (Error) → BLOCKS deployment — fix before
Activate - Priority 2 (Warning) → PM review required before proceeding
- Priority 3 (Info) → Log to task file only
Code Coverage Gate (Step 3)
- New objects (class/program created this task): minimum 70% statement coverage. Below threshold → write additional ABAP Unit tests before proceeding to
RunATCCheck. - Existing objects (modified, not created): coverage must not regress below the value recorded in the last QA report (
deliverables/REQ-NNN-*/04_qa_report.mdif tracked, elsememory/log) for that object. A drop is treated the same as a coverage-threshold miss. - Disposition when coverage cannot reach 70% (e.g. generated/boilerplate code, trivial getters): QA Engineer may waive with an explicit justification recorded in the QA report / memory log — never silently skip.
- Coverage is informational-only for GUI Scripter (BDC/VBS) objects, which
GetCodeCoveragedoes not instrument.
Output Format
Report each step result clearly:
✅ SyntaxCheck — PASSED
✅ RunUnitTests — PASSED (N tests, 0 failures)
✅ GetCodeCoverage — PASSED (82% statement coverage, threshold 70%)
✅ RunATCCheck — PASSED (0 Priority-1, 0 Priority-2, N Priority-3)
If any step fails:
❌ SyntaxCheck — FAILED
Error: <error message>
Line: <line number>
Action required: Fix the syntax error before proceeding.
❌ GetCodeCoverage — FAILED (54% statement coverage, threshold 70%)
Action required: Add ABAP Unit test cases covering the uncovered branches,
or record a waiver with justification in the QA report.
Rules
- Never skip SyntaxCheck — even for "trivial" one-line changes.
- If SyntaxCheck fails, fix the code and re-run before proceeding to RunUnitTests.
- If RunUnitTests fails, do not run GetCodeCoverage or RunATCCheck until the test logic is fixed.
- If GetCodeCoverage falls below threshold (or regresses on an existing object) without a recorded waiver, do not proceed to RunATCCheck.
- Priority-1 ATC findings block all further steps including transport release.
- In Gemini / Antigravity sessions: route all four steps through
sap_executewith"action": "SyntaxCheck","action": "RunUnitTests","action": "GetCodeCoverage","action": "RunATCCheck".
Claude Code Desktop App Note
PostToolUse hooks do not fire automatically in the Desktop App. Run all three steps of this chain manually after each write in Desktop sessions using /post-write <object-name>.
Context
This skill enforces a mandatory four-step quality gate that runs after every ABAP write operation (WriteSource, EditSource, or Activate). The chain ensures that no modified object reaches a transport request or production without passing syntax validation, unit tests, code coverage thresholds, and ATC checks. It is the primary safeguard against regressions in the ABAP development workflow.
When to Use
- After any
WriteSource,EditSource, orActivateoperation on SAP ABAP objects - Automatically triggered by PostToolUse hooks in CLI sessions
- Manually invoked via
/post-write <object-name>in Claude Code Desktop App sessions - Before releasing a transport request
Execution Steps
- SyntaxCheck — Run syntax validation on the modified object. Must return 0 errors to proceed.
- RunUnitTests — Execute all ABAP Unit tests for the object. Must return 0 failures to proceed.
- GetCodeCoverage — Measure statement coverage. New objects require 70% minimum; existing objects must not regress below prior baseline.
- RunATCCheck — Execute ABAP Test Cockpit checks. Priority-1 findings block deployment.
- If any step fails, fix the issue and re-run from the failed step. Do not skip forward.
Related Skills
- abap-dev — Core ABAP development workflows including unit testing and performance analysis
- desktop-app-fallback — Manual QA chain for Desktop App sessions where hooks do not fire
- performance-tuning — Deep performance analysis for slow programs and expensive SQL
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.