doey-scaffy-validate

To validate scaffy templates, parse the .scaffy file to report syntax or structural problems before applying it. This catches errors early in development, review, or CI workflows to prevent runtime failures.

Yes, you can generate JSON validation reports for scaffy templates by enabling the --json flag. This produces machine-readable output suitable for automated CI workflows, allowing pipeline integration to catch structural issues early.

Strict validation mode enforces strict checks to ensure variables, IDs, and anchors are properly defined within scaffy templates. Use it during development and review workflows to enforce higher structural integrity and catch undefined elements.

Run scaffy template validation from a specific working directory by passing the --cwd flag with your target path. This respects an explicit working directory context, ensuring validation operates on the correct template files.

Scaffy template validation catches syntax and structural problems, including undefined variables, IDs, and anchors when using strict mode. It prevents runtime failures by identifying these template issues early across development, review, and CI workflows.

Automated scaffy template linting focuses strictly on syntax and structural integrity, checking .scaffy files for defined variables, IDs, and anchors. It does not validate logical correctness or application-specific behavior beyond structural template validation.