move-code-quality
Check Move Code Quality
Move code reviews require deep knowledge of the Move Book Code Quality Checklist. This skill provides automated analysis against 50 rules for Move 2024 Edition best practices including code organization, function signatures, testing patterns, and modern syntax.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "move-code-quality". Analyze my Move package for quality issues
Expected outcome:
- Move Code Quality Analysis
- Summary: 12 checks passed, 5 improvements recommended, 2 critical issues
- Critical Issue: Missing Move 2024 Edition in Move.toml
- Important: Legacy module syntax detected - use modern semicolon syntax
- Recommendation: Update function parameter ordering - objects should come before primitives
Using "move-code-quality". Review my Move.toml file
Expected outcome:
- Move.toml Analysis Results
- Edition: 2024.beta - Compliant
- Dependencies: Sui framework implicit - Good
- Named Addresses: Properly prefixed with project namespace
- All checks passed
Using "move-code-quality". Check my test module for issues
Expected outcome:
- Test Module Review
- Test attributes: Properly merged #[test, expected_failure]
- Naming: No redundant test_ prefix - Good
- Assertions: Uses assert_eq! where possible - Excellent
Security Audit
SafeThis is a pure prompt-based skill containing only documentation and AI instructions. No executable code, file system access, network calls, or command execution exists in the skill definition. All 139 static findings are FALSE POSITIVES caused by the scanner misinterpreting Move code examples, error constants, and documentation links.
Risk Factors
🌐 Network access (2)
⚡ Contains scripts (2)
⚙️ External commands (110)
Quality Score
What You Can Build
Code Review Before Deploy
Review Move packages against official checklist before mainnet deployment
Blockchain Security Analysis
Audit smart contract code for quality issues and best practice violations
Learn Modern Move Patterns
Get feedback on code while learning Move 2024 Edition standards
Try These Prompts
Analyze my Move package for code quality issues. Check Move.toml configuration, all .move files, and test modules against the Move Book checklist.
Check this Move file for quality issues. Focus on function signatures, parameter ordering, and modern syntax usage.
Review my Move.toml file. Check edition specification, dependencies, and named address configuration.
Review my Move tests. Check test attributes, naming conventions, assertions, and cleanup patterns.
Best Practices
- Run this skill before committing Move code to catch quality issues early
- Focus on critical issues first - Move 2024 Edition is required for modern features
- Use the provided examples to understand both problematic and correct patterns
Avoid
- Skipping this review before mainnet deployment
- Ignoring parameter ordering guidelines - they enable proper composability
- Using outdated explicit framework dependencies in Move.toml