move-code-quality

Run a review of your Move package against the Move Book Code Quality Checklist, which covers 11 categories including manifests, imports, structs, functions, and tests. The analysis reports issues with file paths, line numbers, and corrected code examples.

Move 2024 Edition requires an edition field set to "2024.beta" or "2024" in the package manifest. For Sui 1.45 and later, explicit framework dependencies like Sui, Bridge, and MoveStdlib should be removed since they are implicit.

No, combining public and entry is redundant. Use public functions that return values for composability with Programmable Transaction Blocks, or entry functions only for pure transaction endpoints that transfer objects.

All checklist recommendations assume Move 2024 Edition. If your Move.toml lacks the edition declaration, the analysis flags it as a critical issue because modern syntax features like method chaining and macros require it.

Common issues include prefixing test names with test_, using abort codes in assert! statements, cleaning up expected_failure tests, and using full TestScenario setups when tx_context::dummy() suffices. The review recommends assert_eq! and sui::test_utils::destroy instead.