Checks the structural correctness of the extension: XML format, properties, composition, borrowed objects, role rights. Analogous to /cf-validate, but for extensions.
The sources are checked. Applicability — after loading into the database: /db-cfe-admin check.
Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
| ExtensionPath | yes | — | Path to the extension directory or Configuration.xml |
| ConfigPath | no | — | Directory of the configuration from which objects are borrowed |
| Detailed | no | — | Verbose output (all checks, including successful ones) |
| MaxErrors | no | 30 | Stop after N errors |
| OutFile | no | — | Write the result to a file |
ConfigPath
Always specify when the source configuration is available: without it, some errors in borrowed forms are not caught, and the extension may pass validation and then be rejected by the platform on load.
If the user did not specify a path — determine it yourself:
- Read
.v8-project.jsonfrom the project root - Resolve the target database (by name, branch, or
default) - Take its field
configSrc
Command
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/cfe-validate.ps1" -ExtensionPath "src\cfe\extname"
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/cfe-validate.ps1" -ExtensionPath "src\cfe\extname\Configuration.xml"
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/cfe-validate.ps1" -ExtensionPath "src\cfe\extname" -ConfigPath "src\cf"