umbraco-skill-code-analyzer

You validate Umbraco code examples in markdown by scanning SKILL.md files to detect invalid @umbraco-cms/backoffice imports, unrecognized manifest extension type values, and deprecated TypeScript patterns using static analysis.

Common issues with Umbraco backoffice imports include using unknown @umbraco-cms/backoffice/* module paths falling outside a known allowlist, or specifying unrecognized manifest extension type values within TypeScript code blocks.

Yes, you can compile TypeScript code blocks inside SKILL.md files for error checking by running lightweight TypeScript compilation with stubbed Umbraco modules to catch syntax and type errors.

You detect deprecated Umbraco extension patterns in documentation by applying regex-based deprecation rules to scan markdown code fences and flag specific outdated TypeScript or JavaScript patterns.

Yes, static analysis works for checking Umbraco manifest extension type values by scanning manifest-like code blocks in SKILL.md files and flagging any unrecognized type values against an allowlist.

A limitation of analyzing Umbraco TypeScript examples in markdown is that TypeScript compilation is optional and relies on stubbed Umbraco modules, meaning actual runtime behavior or complex module interactions are not fully validated.