按最近已完成的 8 小时观测回合间的 GitHub 星标增量排序
The whole Maya workflow in Blender, in one install. Free and open source, Blender 4.5 – 5.2.
翻译准备中
SuperClaude for SAP — Claude Code plugin for SAP On-Premise S/4HANA ABAP development (24 agents, 14 skills, 150+ MCP tools)
翻译准备中
取自仓库 README
正在加载完整 README。
查看完整 README ↗Claude Code plugin for SAP ABAP development — SAP ECC / S/4HANA On-Premise / S/4HANA Cloud (Public & Private)
Website: sc4sap.dev
SuperClaude for SAP transforms Claude Code into a full-stack SAP development assistant. It connects to your SAP system via the MCP ABAP ADT server (150+ tools) to create, read, update, and delete ABAP objects directly — classes, function modules, reports, CDS views, Dynpro, GUI status, and more.
| Capability | What it does |
|---|---|
| 🔌 Auto MCP Install | abap-mcp-adt-powerup is auto-installed, configured, and connection-tested during /sc4sap:setup. No manual MCP wiring. |
| 🌐 Multi-Environment Profiles (Dev / QA / Prod) | Register multiple SAP systems per company (e.g. KR-DEV, KR-QA, KR-PRD, US-DEV) and hot-switch between them in-session via /sc4sap:sap-option. QA and Prod profiles are auto-protected: a 2-layer defense (PreToolUse hook + MCP-server guard) blocks Create*/Update*/Delete*, CreateTransport, and runtime code execution tools — bypassing the hook does not bypass enforcement. Passwords are stored in the OS keychain (@napi-rs/keyring — Windows Credential Manager / macOS Keychain / libsecret) so .sc4sap/ never leaks secrets to git. Artifacts (specs, CBO catalogs, audits) are isolated per profile with read-only cross-view so QA sessions can inspect Dev-produced specs without contaminating them. |
| 🏗️ Formatted Auto Program Maker | Builds ABAP programs end-to-end: Main + conditional Includes (OOP/Procedural), full ALV + Docking, Dynpro + GUI Status, mandatory Text Elements, ABAP Unit tests — platform-aware (ECC / S4 On-Prem / Cloud). |
| 🔍 Program Analyze | Read any ABAP object via MCP, run Clean ABAP / performance / security review, or reverse-engineer into Functional/Technical Spec (Markdown/Excel). |
| 🧪 Analyze Code | /sc4sap:analyze-code — dedicated static review pass (sap-code-reviewer): Clean ABAP, performance, security, SAP standard compliance. Severity-ranked findings with concrete fix suggestions. |
| 🔀 Compare Programs | /sc4sap:compare-programs — side-by-side business comparison of 2–5 ABAP programs that share the same scenario but split by module (MM/CO), country (KR/EU), or persona (controller/warehouse). Consultant-facing editable HTML report across 10 configurable dimensions — coloured verdict matrix with a Differences only switch, field-by-field differences, screens drawn side by side, decision guide, versions + English companion. |
| ⚙️ Config → Document | /sc4sap:config-to-document — one module's configuration documented as it is in the connected system (MM first). One offline HTML file that follows the IMG tree: per IMG activity the real table values drawn on an SM30-style screen, rows changed by customer transports with their transport history, configuration checks, SAP's IMG documentation, and consultant notes written by the module consultant agent and reviewed by sap-critic. Read-only on SAP; an in-page edit mode lets the consultant correct the notes, values and change history and hand the file back for the next version. |
| 🔌 Interface Mapping Spec | /sc4sap:interface-mapping-spec — interface mapping specification as one editable HTML page in the classic template layout: cover, revision history, Source → Target field grid with conversion-rule and MAPPING columns, synchronous response block, extraction condition, field guide. Built for new interfaces: scenario presets, SAP fields from a TABLE-FIELD list or the module consultant's proposal (checked against DDIC) — or read from an existing table, structure, view or RFC — with the counterpart side, DB types and conversion rules proposed. In-page checks (missing items, truncation, type and key mismatches, unmapped fields), Excel paste, versions with revision history, English companion, refresh when the SAP structure changes. |
| 🖨️ SmartForm Preview | /sc4sap:smartform-preview — the expected print of a SmartForm as a JPG, without a print program or test data: windows at their real mm positions, SmartStyle fonts, template grids with borders and shading, SE78 graphics (logo, signature), loops with sample rows. The &fields& get invented sample values sized to their DDIC types, and the report lists the cells and windows whose content is cut off. Read-only. → smartforms/<FORM>/<FORM>-preview.{jpg,html} |
| 📄 SmartForm from PDF | /sc4sap:smartform-from-pdf — builds a SmartForm from a PDF (or screenshot) of the printed form: ruled areas become templates, every text sits where the source has it in the closest format of an existing SmartStyle, then the values become &fields&, item lines a loop over an internal table and the interface is added — decided with you. Uploaded to the DEV system, printed there and scored against the source page. → smartforms/<FORM>/ |
| 📊 Project Dashboard | /sc4sap:project-dashboard — one editable HTML page per SAP project for the PM and the PMO (summary, KPIs, milestones with Q-gates, WBS with Gantt, team, history) plus a portfolio page over every project. Templates for new implementation (SAP Activate), S/4 conversion, rollout, AMS release and small projects; module and development consultants tracked separately (WRICEF stages, hand-off queue); actuals read from the connected system (transports split into customizing vs workbench, package objects, inactive objects, dumps after go-live). Members join and leave by date; open items of leavers are flagged. Spreadsheet-style editing, works on mobile. → projects/<CODE>/ |
| 🔐 Role Matrix | /sc4sap:role-matrix — the project's role & authorization document as one editable HTML workbook: cover with checks, business roles, PFCG roles, business role × T-code matrix (F/C/D), user × role assignment, authorization objects, SoD rules with automatic conflict check, change history. New design from the module consultant's proposal (narrowed to the T-codes users run when ST03N usage is available) or read from SAP (roles, T-codes, authorization values, org levels, user assignment by user ID only — no user master data). Large systems are paged; search, CSV and paste cover the whole sheet. Read-only on SAP. → roles/<CODE>/ |
| 🗺️ Module → Process | /sc4sap:module-to-process — one editable HTML process map per module, built only from the TCodes users actually run (productive ST03N): CBO programs of all the module's packages placed on the standard L1–L4 process backbone with variants, owners and systems, an L3 scenario swimlane each, and a PDD-style task sheet per L4 (business rules with source lines, steps, related objects, interfaces, S/4 conversion notes); optional module-consultant review, existing-BPH reconciliation and English companion. Replaces package-to-process (kept one release as a redirect) |
| 🩺 Maintenance Diagnosis | Operational triage loop: ST22 dumps, SM02 system messages, /IWFND/ERROR_LOG, profiler traces, logs, where-used graphs — all from Claude. |
| 🕸️ CBO Relation Map | /sc4sap:cbo-relation-map — one HTML page per package that shows how its customer objects relate, drawn from the analyze-cbo-obj graph without a SAP call: tables → data elements → domains, check tables, search helps, view bases, and programs / function modules reading and writing tables. Most connected objects, groups of related objects, a neighbourhood view with filters, the shortest path between two objects, and the DDIC row or source line behind every relation. Standard objects are left out. → cbo/<MODULE>/<PACKAGE>/<PACKAGE>-relation-map-{ko,en}.html |
| ♻️ CBO Reuse (Brownfield Accelerator) | Inventory a Z-package once — create-program / program-to-spec prefer reusing existing CBO assets over duplicates. |
| 🧷 CBO Extension Awareness (CMOD / GGB0·1 / BTE / VOFM / BAdI / APPEND) | Inventories user-exits (CMOD), validations & substitutions (GGB0/GGB1), BTE function modules, VOFM routines (requirements / formulas / data transfer), BAdI implementations, and APPEND structures. create-program / BAPI flows prefer existing Extension fields (e.g. BAPI EXTENSIONIN / table appends) over new CBOs; dump & incident diagnosis inspects Extension points as first-class suspects. |
| 🏭 Industry Context | 14 industry reference files (retail, fashion, cosmetics, tire, automotive, pharma, F&B, chemical, electronics, construction, steel, utilities, banking, public-sector). |
| 🌏 Country / Localization | 15 per-country files + EU-common (KR/JP/CN/US/DE/GB/FR/IT/ES/NL/BR/MX/IN/AU/SG). e-invoicing, banking, payroll, tax localization. |
| 🧩 Active-Module Awareness | Cross-module integration hints: MM + PS active → auto-suggest WBS fields on MM CBOs; SD + CO active → CO-PA derivation. Details → |
| 🤝 Module Consultation | sap-analyst / sap-critic / sap-planner / sap-architect delegate to 14 module consultants + 1 BC consultant when business judgement is needed. Users can also ask a module consultant directly via /sc4sap:ask-consultant — auto-routes SD/MM/FI/CO/PP/PS/PM/QM/TR/HCM/WM/TM/BW/Ariba/BC by keywords, answers against the configured SAP environment (version, industry, country, active modules), read-only. |
| ⚡ Per-Phase Model Routing | Every skill's main thread follows your session model (model: inherit) while delegating heavy work to specialized agents (Opus for novel ABAP generation, cross-module synthesis, and incident triage; Sonnet for facts extraction; Haiku for report rendering). No skill switches the main thread, so your model choice holds and the prompt cache is never re-written mid-session; per-phase Agent() dispatches run on their declared tier. Model choice is visible in every response prefix + per-phase banner (e.g. ▶ phase=3 (writer-spec) · agent=sap-writer · model=Opus). Full matrix — per-skill, per-phase — in docs/skill-model-architecture.md. |
This project was inspired by oh-my-claudecode by 허예찬 (Hur Ye-chan). The multi-agent orchestration patterns, Socratic deep-interview gating, persistent loop concepts, and overall plugin philosophy here all trace back to that work.
mcp-abap-adt by fr0ster was a major contribution to building our customized MCP server (abap-mcp-adt-powerup). The pioneering ADT-over-MCP work — request shaping, endpoint coverage, object I/O — provided the conceptual foundation we drew on while designing and extending our own server.
