xojo-lint

What problem does it solve? Xojo projects saved in text format can silently break through malformed #tag regions, mismatched designer Begin/End blocks, duplicate manifest item IDs, or missing companion files, and the Xojo IDE only surfaces these problems late. This Skill catches broken .xojo_* files before the IDE sees them and repairs safe serialization details automatically. ## Core Features & Use Cases - Structural validation: The check command validates UTF-8 text containers, #tag and Begin/End structure, project manifest rows and item relationships, resource chunk boundaries, UI-state records, and library archives, reporting error, warning, and notice severities with editor-friendly path:line:column output. - Conservative formatting: The format command normalizes serializer tag case and nesting, repairs missing source indentation, removes whitespace around manifest keys, and adds missing final line breaks, without reordering properties or rewriting Xojo expressions, identifiers, comments, or string literals. - Pre-commit integration: A ready-to-use git hook lints staged .xojo_* files and blocks commits on errors, warnings, or files the formatter would change. - Use Case: After an agent edits a .xojo_window file, run check --all and format --check on the project to confirm the serialization is intact before opening it in the Xojo IDE. ## Quick Start Ask the agent to lint and format-check your Xojo project, for example: run xojo-lint check and format --check on this Xojo project and fix anything it reports.