validate-mojo-patterns

Validate Mojo constructor patterns by using the validate-mojo-patterns skill to check for correct usage of `out self` versus `mut self` and other constructor conventions. The skill identifies violations like incorrect transfer semantics and suggests fixes to ensure your code compiles and follows language best practices.

Pattern validation checks Mojo constructor shapes, method signatures, ownership rules, trait conformances, and transfer semantics. It enforces language conventions across code reviews and pre-commit validation, catching issues that reduce maintainability and create compilation errors.

Yes. Use pattern validation during code review to quickly identify incorrect Mojo patterns like misused constructors, broken ownership semantics, or non-conformant traits. The skill pinpoints violations and suggests fixes before code reaches production.

Pattern validation integrates as pre-commit validation and during package builds via `mojo package`. It extracts patterns, categorizes them, identifies violations, applies fixes, and validates the packaged result to ensure your entire codebase meets project standards.

Mojo pattern validation works with Mojo source files and uses `grep` for pattern extraction. It validates code across the codebase and outputs results compatible with package validation workflows.