sap-fix-incidentlisted

Closes the loop from a /sap-diagnose root cause to a deployed, test-verified fix — conservatively and test-first. Takes a diagnose deliverable (or a dump key) whose top hypothesis is a CUSTOM-CODE DEFECT, acquires the failing source, reasons a minimal patch, reproduces the defect as a RED ABAP Unit test (via /sap-gen-abap-unit), applies the patch, re-checks with /sap-check-abap, deploys to a modifiable DEV system behind a transport, and proves the test GREEN with /sap-run-abap-unit. HARD GUARD RAILS: only custom-code-defect hypotheses on Z*/Y* objects; never patches SAP standard (→ Note/enhancement, analysis only); never writes to a non-modifiable / production system — the fix is made in DEV and handed to /sap-transport-readiness → /sap-se01 release → /sap-stms. Deploy is gated (Rule 2): default is to PROPOSE a diff and wait for confirmation. Prerequisites: a /sap-diagnose deliverable or a dump; pinned DEV /sap-login profile + active GUI session; SAP NCo 3.1 (32-bit) for RFC.
sapdev-ai/sap-dev · ★ 7 · Code & Development · score 73

Install: claude install-skill sapdev-ai/sap-dev

# SAP Fix Incident Skill (diagnose -> fix closed loop) You turn a root-caused incident into a **deployed, test-verified** source fix — the last mile `/sap-diagnose` deliberately leaves open (it is read-only). The *reasoning* (what is broken and the minimal patch) is yours; the *acquire / test / deploy / activate / verify* half reuses skills that are already live-tested. You are conservative by construction: you fix only custom code, only in DEV, only behind a transport, and only after a confirmation gate — and you never claim a fix you did not prove with a red->green test transition. Task: $ARGUMENTS This skill observes `shared/rules/skill_operating_rules.md`. **Rule 2 (no unsolicited deployment) is central**: everything up to the patch is read-only; the deploy is gated behind `--apply` (default = PROPOSE + confirm). It is the write-capable companion to the read-only `/sap-diagnose`. --- ## Shared Resources | File / token | Path | Purpose | |---|---|---| | `safety_policy.md` | `<SAP_DEV_CORE_SHARED_DIR>\rules\safety_policy.md` | **Rule 0 (highest priority)** — environment guard; Step 0.6 runs `sap_safety_gate.ps1 -Action assert` | | `skill_operating_rules.md` | `<SAP_DEV_CORE_SHARED_DIR>\rules\skill_operating_rules.md` | Rule 1 (no write SQL on standard tables) + Rule 2 (no unsolicited deploy) — the confirmation gate | | `tr_resolution.md` | `<SAP_DEV_CORE_SHARED_DIR>\rules\tr_resolution.md` | TR is resolved ONLY via `/sap-transport-request` | | `abap_code_quality_rules