abap2ui5-check

Run the abap2UI5 gates on: the text after the command

1. Scope

• An argument names the files or folder to check.
• Without one: the .clas.abap / .clas.xml files that git status --porcelain and git diff --name-only report as changed or new. Nothing changed (or no git): the whole src/ folder. Say which scope you took.

2. Run the gates

Pick the first that applies:

1. The project has app-template's scripts (package.json has a check script that runs abaplint and abap2ui5lint): npm run check:abap and npm run check:abap2ui5, as two commands - npm run check chains them with &&, so an abaplint finding (a missing BOM is one) hides every linter finding until it is fixed. Both lint the whole project; report the findings in scope first. Without node_modules, run npm ci first (ask before installing).
2. Otherwise, two commands:
   • abaplint, when the project has an abaplint.json / abaplint.jsonc: npx --yes @abaplint/cli <that file>. Without one, skip it and say so - do not invent a config.
   • the abap2UI5 linter: npx --yes @abap2ui5/linter <files or folder> (add --no-render when the render gate is not installed and says so). It honours the project's abap2ui5lint.jsonc.
3. No shell, or npm unavailable, but the MCP server is there: validate_view { abap_source, project_dir } per class. That covers the linter, not abaplint - say so.

3. Explain

For every finding: file:line, the rule id, what it means in one sentence, and the fix. The linter explains its own rules (npx --yes -p @abap2ui5/linter abap2ui5lint --explain <rule-id>, or validate_view { explain: true }). Group by file; errors before warnings before hints.

Then go over what the gates cannot see, using the abap-check and ui5-check skills (MCP pitfalls lists both): the .clas.xml byte format (BOM, LF, final newline, <CLSNAME>, <WITH_UNIT_TESTS>, '), activation traps, icons and controls that do not exist in UI5 1.71. Report only what you actually find in the files in scope.