Sapui5 Linter
- Updated May 19, 2026
- AndreaFusar/https-github.com-secondsky-sap-skills
sapui5-linter is an agent skill that guides @ui5/linter setup, rule runs, autofix, and CI integration for SAPUI5/OpenUI5 codebases.
About
sapui5-linter is an agent skill for developers maintaining SAPUI5 or OpenUI5 applications and libraries who need repeatable static analysis beyond ad-hoc IDE warnings. It walks through installing and configuring the UI5 Linter, tuning rules for your codebase, running scans that surface deprecated APIs, unsafe globals, Content Security Policy gaps, and manifest.json problems, and applying autofix where the tool supports it. developers on Fiori-style enterprise frontends use it during active feature work and again before releases when CI must fail on regressions. The skill also frames pre-commit hooks and pipeline integration so lint results stay aligned with UI5 2.x migration efforts. It assumes you already have a UI5 project structure—not greenfield framework choice—and focuses on analysis, remediation, and enforcement rather than visual design.
- Covers @ui5/linter setup, rule configuration, and project-wide runs
- Detects deprecated APIs, global variables, CSP violations, and manifest issues
- Autofix for deprecated APIs, globals, event handlers, and manifest properties
- Documents CI/CD integration and pre-commit hook patterns
- Supports UI5 2.x migration preparation workflows
Sapui5 Linter by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add AndreaFusar/https-github.com-secondsky-sap-skills/plugin install sapui5-linter@sap-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | May 19, 2026 |
|---|---|
| Repository | AndreaFusar/https-github.com-secondsky-sap-skills ↗ |
What it does
Run @ui5/linter on SAPUI5/OpenUI5 apps to catch deprecations, CSP issues, and manifest problems—with autofix and CI hooks—for safer UI5 2.x migration.
Who is it for?
Best when you're maintainers of Fiori-style UI5 apps and need migration-aware linting with autofix and pipeline enforcement.
Skip if: Non-UI5 React or Vue stacks, greenfield UI framework selection, or teams without any SAPUI5/OpenUI5 codebase.
When should I use this skill?
Use when working with the UI5 Linter (@ui5/linter) for static code analysis, configuration, autofix, or CI/CD integration on SAPUI5/OpenUI5 projects.
What you get
You get configured lint runs, actionable findings, autofixed code where supported, and CI or pre-commit patterns that keep UI5 quality stable toward 2.x.
- Configured linter setup and rule set
- Lint report with categorized findings
- Autofixed source and manifest changes where supported
By the numbers
- Targets UI5 2.x migration preparation alongside current-version deprecations
- Autofix coverage includes deprecated APIs, globals, event handlers, and manifest properties
Files
Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. Covers setup, configuring linting rules, running the linter to detect deprecated APIs, global variable usage, CSP violations, and manifest issues. Supports autofix for deprecated API usage, global references, event handlers, and manifest properties. Includes CI/CD integration, pre-commit hooks, and UI5 2.x migration preparation.
sapui5-linter
Source: ./plugins/sapui5-linter
{ "name": "sapui5-linter", "source": "./plugins/sapui5-linter", "license": "GPL-3.0", "version": "2.2.0", "category": "ui-development", "keywords": [ "api", "components", "fiori", "frontend", "linter", "migration", "mvc", "sapui5", "sapui5-linter" ], "description": "Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. Covers setup, configuring linting rules, running the linter to detect deprecated APIs, global variable usage, CSP violations, and manifest issues. Supports autofix for deprecated API usage, global references, event handlers, and manifest properties. Includes CI/CD integration, pre-commit hooks, and UI5 2.x migration preparation." }
Related skills
Vercel React Best PracticesAutomatically apply Vercel’s official React and Next.js performance rules during code generation and review.587k29.6kVercel Composition PatternsGenerate and refactor React components that stay maintainable as complexity grows without boolean prop explosion.267k29.6k
ShadcnAdd, compose, search, fix, and style production-grade React components directly from source without leaving their editor.257k120k
Develop UserscriptsCorrectly write, debug, and package userscripts for Tampermonkey and ScriptCat with proper metadata, GM APIs, and runtime decisions.224k72
Minimalist UiGenerate clean, editorial-style web interfaces with warm monochrome palettes, typographic hierarchy, bento grids and flat components that feel premium and utilita212k69.4kImage To CodeConvert high-fidelity design images into production-ready, visually accurate frontend code that avoids generic AI design pitfalls.177k69.4kHow it compares
Enterprise UI5-specific static analysis skill—not a generic ESLint or general frontend accessibility checker.
FAQ
Who is sapui5-linter for?
It is for developers working on SAPUI5 or OpenUI5 applications and libraries who use or want to adopt @ui5/linter for deprecation and manifest hygiene.
When should I use sapui5-linter?
Use it while building UI5 views and controllers, before merging large refactors, when wiring CI or pre-commit checks, and while preparing for UI5 2.x migration—not only on day one of a unrelated stack.
Is sapui5-linter safe to install?
Autofix and CI steps can rewrite source and manifest files; review the Security Audits panel on this Prism page and run the linter on a branch with backups before enabling aggressive autofix in main.