sap-docs-convertlisted

Applies customer-specific normalisation rules to the extracted spec files in a work folder. Reads `spec_conversion_rules.tsv` (default at sap-dev-core/shared/tables/, override at {custom_url}/spec_conversion_rules.tsv) and rewrites the affected `_*.txt` files in place. Three rule categories: * field_rename — legacy field name → canonical name * type_rename — legacy DDIC type token → canonical token * flag_mapping — legacy flag value → one or more KEY=VALUE pairs Plus optional schema migration (legacy customer YAML/TSV layout → Customer Brief layout). Input: work folder containing the extracted `_*.txt` files (output of /sap-docs-extract). Output: same files rewritten in place; a `.pre-convert/` snapshot is taken first. This skill is OPTIONAL — projects already authoring specs in Customer Brief format can skip it entirely.
sapdev-ai/sap-dev · ★ 4 · Data & Documents · score 77

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

# SAP Docs Convert Skill You normalise an extracted spec by applying customer-specific rules. Runs between `/sap-docs-extract` and the validation / generation skills: ``` spec.xlsx ──[sap-docs-extract]──▶ raw _*.txt │ ▼ ──[sap-docs-convert]── (optional, rules-driven) │ ┌────────────────────┼─────────────────────┐ ▼ ▼ ▼ /sap-docs-check-ddic /sap-docs-check-process /sap-gen-abap ``` Task: $ARGUMENTS --- ## Shared Resources | File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI-scripting language independence — offline normaliser, but rule applies to downstream deploy skills the converted spec feeds | | `<SAP_DEV_CORE_SHARED_DIR>/rules/abap_code_quality_rules.md` | ABAP code-quality rules — type-rename and flag-mapping rules that convert legacy spec fields into Customer Brief layout must preserve ABAP-quality affordances (DTEL vs. primitive, currency reference) so the generated code stays clean | --- ## Step 0 — Resolve Work Directory and Rules File **Settings reads/writes follow `<SAP_DEV_CORE_SHARED_DIR>/rules/settings_lookup.md`** — merge `settings.local.json` over `settings.json` per-key on the `.value` field; writes always