move-code-quality

Move 2024 Edition compliance checking validates modern syntax, dependencies, and naming conventions across your Move.toml manifest and .move sources. It identifies compliance gaps and provides actionable remediation guidance to align your package with edition requirements.

Linting Move source files involves running automated code quality analysis across formatting, imports, structs, functions, and tests. This process surfaces actionable improvements and reduces debugging time by validating patterns against the Move Book Code Quality Checklist.

Yes, you can perform category-specific analyses instead of a full package scan. The workflow supports targeted checks based on user intent, enabling validation of specific areas like manifest constraints, imports, structs, functions, macros, tests, or documentation patterns.

Yes, a Move.toml manifest is required to run code quality checks. The analyzer applies to Move projects with Move.toml manifests and .move sources, validating manifest edition, dependencies, and named addresses alongside source code patterns.

Move packages fail code quality checks on struct definitions due to readability, safety, or composability issues. The analyzer reviews struct patterns against the Move Book Code Quality Checklist and provides actionable remediation guidance to resolve identified gaps.