From sc4sap
Reviews ABAP objects via AST, semantic, and where-used analysis with rule-based scoring. Use before releasing transports or when taking over existing SAP code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sc4sap:analyze-codesonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reviews an ABAP object by delegating the heavy work (source read, structural/semantic/where-used analysis, 14-dimension rule matching) to `sap-code-reviewer` (Opus 4.7). The main thread only handles Socratic intake, report formatting, and the follow-up action menu — all on Haiku for cost efficiency.
Reviews an ABAP object by delegating the heavy work (source read, structural/semantic/where-used analysis, 14-dimension rule matching) to sap-code-reviewer (Opus 4.7). The main thread only handles Socratic intake, report formatting, and the follow-up action menu — all on Haiku for cost efficiency.
<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>
<Phase_Banner>
Multi-phase skill. Before each Agent(...) dispatch, emit ▶ phase=<id> (<label>) · agent=<name> · model=<Opus 4.7|Sonnet 4.6|Haiku 4.5> per ../../common/model-routing-rule.md § Phase Banner Convention.
</Phase_Banner>
<Team_Mode>
Type B (Coder ↔ Consultant) teamMode activates between Step 2 (reviewer full review) and Step 3 (report) when reviewer's findings include a business-alignment dimension (§ 1 Business Purpose, § 2 Rule Faithfulness, § 13 Cross-Module Side-Effects) AND the object touches 2+ modules. Reviewer becomes Worker, module consultants become Peers; consultants live-validate the reviewer's business-alignment findings. See team-mode.md. Base protocol: ../../common/team-consultation-protocol.md § Type B.
</Team_Mode>
<Use_When>
<Do_Not_Use_When>
/sc4sap:create-program (full program flows) or direct UpdateClass / UpdateProgram / UpdateInclude MCP calls/sc4sap:create-objectReadClass, ReadProgram etc. directly
</Do_Not_Use_When><Session_Trust_Bootstrap> MANDATORY — runs as Step 0 before any MCP call or user interaction.
Invoke /sc4sap:trust-session with parent_skill=sc4sap:analyze-code to pre-grant all MCP tool + file-op permissions for this session (eliminates per-tool "Allow this tool?" prompts during the review flow).
.sc4sap/session-trust.log already has a line within the last 24h, skip silently.Agent dispatches within this skill MUST pass mode: "dontAsk".Full spec: see ../trust-session/SKILL.md.
</Session_Trust_Bootstrap>
<Companion_Files> MANDATORY: Read the companion files below before executing.
| Companion | Scope |
|---|---|
analysis-dimensions.md | 9 common/ rule files that the reviewer agent (not main) loads + 14 evaluation dimensions |
workflow.md | 4-step execution flow: Identify → Review (delegated) → Report (branching) → Actions |
output-and-tools.md | Report output format + MCP tool list used by the reviewer agent |
| </Companion_Files> |
<Execution_Summary>
Orchestration is 1 main-thread Socratic intake + one delegated dispatch to sap-code-reviewer + a branching report + main-thread action menu.
SearchObject.sap-code-reviewer with only the object reference. The reviewer agent itself reads source (via GetClass/GetProgram/GetProgFullCode/...), runs structural analysis (GetAbapAST + GetAbapSemanticAnalysis + GetWhereUsed), loads the 9 common/ rule files, and evaluates all 14 dimensions. Returns: findings list (severity · location · rule ref · fix suggestion) + summary metrics.output-and-tools.md.sap-writer (Haiku) for a rich reader-facing report with code examples and impact explanations. Fallback to Branch A on writer failure.sap-executor (user's choice).Full spec in workflow.md. Main thread NEVER calls ReadClass / GetAbapAST / GetWhereUsed directly — that context stays inside the reviewer agent so the orchestrator window remains small even for large objects.
</Execution_Summary>
Task: {{ARGUMENTS}}
npx claudepluginhub babamba2/superclaude-for-sap --plugin sc4sapChecks ABAP code quality with abaplint static analysis and Clean ABAP manual review. Lints syntax, validates best practices, and helps configure abaplint.json.
Explains ABAP objects with full dependency context via SAPContext and optional ATC code quality analysis. Supports classes, CDS views, behavior definitions (BDEF), reports, and more.
Analyzes SAP CBO packages to inventory custom ABAP elements (tables, function modules, classes, etc.) and saves a reference file for reuse across downstream development skills.