move-code-quality — Claude Code skill: Move code review
Checks Move packages against the Move Book code quality checklist and flags what breaks Move 2024 Edition rules.
npx claude-code-templates@latest --skill development/move-code-qualityWhat move-code-quality does
The skill fires on its own when a project contains .move files or a Move.toml manifest. It then walks the code against the Move Book checklist: 11 categories, 50+ rules. You get findings tied to specific lines instead of vague style talk.
It starts with the package manifest — whether edition = "2024.beta" or edition = "2024" is set, whether framework dependencies are still listed explicitly, whether named addresses carry a project prefix. Then it reads the code: imports and constants, structs, functions, function bodies, Option macros. It will tell you to write ctx.sender() instead of tx_context::sender(ctx), or id.delete() instead of object::delete(id).
One thing to know up front: without Move 2024 Edition most checklist rules simply do not apply, since the syntax differs. Parameter order is checked strictly too — objects first, TxContext last, Clock just before it. On an older package you are not ready to rewrite, expect a long list of findings.
The skill only analyses and suggests. It does not edit your code.
What it helps with
- audit a Move package against the Move Book checklist
- spot legacy module syntax with braces instead of the label form
- see what blocks a move to Move 2024 Edition
- fix function parameter order for Sui conventions
- drop explicit framework dependencies from
Move.toml
Example prompts for the agent
- check the code quality of this Move package
- go through the
.movefiles and tell me what breaks the checklist - look at
Move.toml— is the edition set correctly?
How to install move-code-quality
1claude-code-templates
npx claude-code-templates@latest --skill development/move-code-quality2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill move-code-quality -a claude-code3Manually: put the files in place
~/.claude/skills/move-code-quality/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/move-code-quality/
Manually: put the files in place
.agents/skills/move-code-quality/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/move-code-quality/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates move-code-quality2Manually: put the files in place
.github/skills/move-code-quality/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/development/move-code-qualityManually: put the files in place
.devin/skills/move-code-quality/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about move-code-quality
How do I install move-code-quality in Claude?
Run npx claude-code-templates@latest --skill development/move-code-quality. Or use npx skills add davila7/claude-code-templates --skill move-code-quality -a claude-code. The skill file lands at ~/.claude/skills/move-code-quality/SKILL.md.
What does move-code-quality do?
It checks a Move package against the Move Book quality checklist: manifest, imports, structs, functions, Option macros. Findings point at specific lines.
When does the skill activate by itself?
When you work with .move files or a Move.toml manifest. You can also ask for a review directly.