القائمة
Diagnose SC4SAP plugin health, MCP server connectivity, and SAP system connection (renamed from `doctor` to avoid conflict with Claude Code's built-in `/doctor`)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reverse-engineer an ABAP program into a Functional/Technical Specification artifact (Markdown or Excel). Socratic scope narrowing from "everything" to "only what the user needs".
Create ABAP programs (Report/CRUD/ALV/Batch) with Main+Include structure, OOP or Procedural, and full agent-driven coding/QA pipeline
Analyze a CBO (Customer Business Object) package — discover frequently-used Z tables / function modules / data elements / classes / structures / table types — and save a per-module / per-package reference file so later `program` / `program-to-spec` runs prefer existing CBO elements over new ones.
ABAP code analysis — delegate source reads + AST/semantic/where-used analysis + rule-based review to sap-code-reviewer, then optionally render a rich briefing via sap-writer
Step-by-step root cause analysis for SAP operational errors. Uses MCP to directly inspect dumps, logs, transports, and where-used relations, then narrows hypotheses with minimal user questions and provides SAP Note search keywords.
Direct operational Q&A with a SAP module consultant agent. Auto-routes the question to the matching sap-{module}-consultant and answers against the configured SAP environment (version, industry, country, active modules).
| name | sc4sap:sap-doctor |
| description | Diagnose SC4SAP plugin health, MCP server connectivity, and SAP system connection (renamed from `doctor` to avoid conflict with Claude Code's built-in `/doctor`) |
| level | 2 |
| model | haiku |
Diagnoses the full SC4SAP stack: plugin installation, MCP server status, and live SAP system connectivity. Reports findings with actionable fixes for each issue found.
sc4sap:sap-doctor runs a structured health check across three layers: the SC4SAP plugin itself, the mcp-abap-adt MCP server registration, and the live SAP system connection. It surfaces problems with clear remediation steps so you can get back to development quickly.<Response_Prefix>
Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention.
</Response_Prefix>
<Use_When>
<Diagnostic_Checks>
MANDATORY: Run the diagnostic checklist defined in diagnostic-checks.md. It covers Layer 1 (Plugin Health) → Layer 2 (MCP Server) → Layer 3 (SAP System Connection) → Layer 4 (Required ABAP Objects — gated on Layer 2 + 3 PASS) → Layer 5 (Configuration) → Layer 6 (RFC Backend, conditional) → Layer 7 (Cache Hygiene, always runs). Report PASS / FAIL / WARN / INFO per layer in the order defined there.
</Diagnostic_Checks>
<Cache_Management>
/sc4sap:sap-doctor accepts two cache flags passed via {{ARGUMENTS}}:
--prune — after running the normal diagnostic report, invoke node "<plugin>/scripts/prune-cache.mjs" (dry-run) and render its output directly. No files are deleted.--prune --yes — after the normal report, invoke the script with --yes to actually delete every stale version directory.Always show the ACTIVE version first and explicitly exclude it from deletion. If no stale versions exist, print "Cache is clean — nothing to prune." and return. If the script exits non-zero, surface the stderr verbatim in the doctor report and do NOT swallow the failure. </Cache_Management>
<Output_Format>
SC4SAP Doctor Report
====================
Plugin Health [PASS] v0.2.2 (cache matches marketplace)
MCP Server [PASS] plugin:sc4sap:sap responding, bridge preflight OK
SAP Connection [PASS] SID=S4H · Client=100 · User=PAEK
Required Objects [WARN] 9a: 3/3 · 9b: 7/7 (ZCL_S4SAP_CM_ALV inactive)
Configuration [PASS]
Cache Hygiene [WARN] 3 stale versions consuming 1.7 GB (0.5.4, 0.6.0, 0.6.1)
Issues Found: 0 errors, 2 warnings
Fix: Activate ZCL_S4SAP_CM_ALV, or re-run /sc4sap:setup wizard step 9b
/sc4sap:sap-doctor --prune --yes (reclaim 1.7 GB)
Second example — connectivity failure gating Layer 4:
SC4SAP Doctor Report
====================
Plugin Health [PASS] v0.2.2
MCP Server [FAIL] plugin:sc4sap:sap not responding
SAP Connection [SKIP] Cannot test without MCP server
Required Objects [SKIP] SAP connection not ready
Configuration [WARN] No .sc4sap/config.json found
Cache Hygiene [PASS] 0 stale versions
Issues Found: 1 error, 1 warning
Fix: Run /sc4sap:mcp-setup to install and register plugin:sc4sap:sap
</Output_Format>
<Remediation_Routing>
/reload-plugins, then restart Claude Code/sc4sap:mcp-setup/sc4sap:mcp-setup Troubleshooting section/sc4sap:setup (wizard step 9a)/sc4sap:setup (wizard step 9b)/sc4sap:setup wizard/sc4sap:sap-doctor --prune to preview, then /sc4sap:sap-doctor --prune --yes to deleteTask: {{ARGUMENTS}}