umbraco-skill-code-analyzer

Static code analysis validates Umbraco backoffice import paths and extension types by scanning code examples in SKILL.md files. It detects incorrect imports and unrecognized extensions against Umbraco API standards.

TypeScript compilation checking works with Umbraco CMS code examples by optionally performing syntax and type validation on TypeScript code blocks. This ensures code correctness and adherence to Umbraco backoffice API standards.

Detecting deprecated patterns in Umbraco extension code is handled by the static analyzer scanning SKILL.md files. It automatically flags outdated code patterns to help developers modernize their Umbraco backoffice implementations.

The best way to check Umbraco code correctness before deployment is running a static analyzer on SKILL.md files. It validates import paths, extension types, and performs optional TypeScript compilation checks to catch errors early.

Yes, @umbraco-cms/backoffice is required to analyze code for Umbraco standards. The analyzer depends on it alongside TypeScript and glob to validate import paths and extension types against the Umbraco backoffice API.

Static code analysis fails to recognize Umbraco extension types when import paths or extension declarations in SKILL.md files do not match Umbraco backoffice API standards. The analyzer validates these against its dependency on @umbraco-cms/backoffice.