move-code-quality
Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.
pinned to #6813ac5updated 2 weeks ago
Ask your AI client: “install skills/move-code-quality”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/move-code-qualitymetahub onboarded this repo on the author's behalf.
If you own github.com/1NickPappas/move-code-quality-skill on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
22
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
You are an expert Move language code reviewer with deep knowledge of the Move Book Code Quality Checklist. Your role is to analyze Move packages and provide specific, actionable feedback based on modern Move 2024 Edition best practices.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.6813ac5· 2 weeks ago
Documentation
41Description quality
41 words · 291 chars — "Analyzes Move language packages against the official Move Book Code Quality Chec…"
README is present and substantial
3,289 chars · 10 sections · 4 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Installation · Usage · Example
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent6813ac5warn2 weeks ago
Contents
A Claude Code skill that analyzes Move language packages against the official Move Book Code Quality Checklist, helping you write better, more maintainable Move code.
Overview
This skill extends Claude Code with deep knowledge of Move language best practices, providing:
- Automated code quality analysis against 10+ categories of best practices
- Specific, actionable recommendations with examples from the Move Book
- Move 2024 Edition compliance checking
- Package manifest validation
- Function signature and structure analysis
- Testing best practices review
What It Checks
The skill analyzes your Move code across multiple dimensions:
- Code Organization - Formatting consistency
- Package Manifest - Edition requirements, dependencies, named addresses
- Imports & Modules - Modern syntax, naming conventions
- Structs - Capability patterns, event naming, dynamic fields
- Functions - Visibility modifiers, composability, parameter ordering
- Function Bodies - Method chaining, string operations, collections
- Option & Loop Macros - Modern idiomatic patterns
- Testing - Attribute usage, assertions, cleanup patterns
- Documentation - Comment quality and completeness
Installation
From Claude Code
# Clone to your Claude skills directory
git clone https://github.com/1NickPappas/move-code-quality-skill ~/.claude/skills/move-code-quality
Manual Installation
-
Create the skills directory if it doesn't exist:
mkdir -p ~/.claude/skills -
Clone or copy this skill to the skills directory:
cd ~/.claude/skills git clone https://github.com/1NickPappas/move-code-quality-skill -
Claude Code will automatically load the skill when working with Move code
Usage
The skill activates automatically when you're working with Move code. You can also explicitly invoke it:
Analyze this Move package for code quality issues
Review this module against the Move code quality checklist
Check if this code follows Move 2024 best practices
Examples
The skill provides specific feedback based on the Move Book examples:
-
Before:
use my_package::{Self}; -
After:
use my_package; -
Reason: Avoid redundant Self imports
-
Before:
public entry fun transfer(...) -
After:
public fun transfer(...) -
Reason: Public functions are more composable for PTBs
Requirements
- Claude Code CLI
- Move 2024 Edition projects
- Basic familiarity with Move language
Contributing
We welcome contributions! Please see CONTRIBUTING.md for details.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Resources
Acknowledgments
This skill is based on the comprehensive code quality guidelines from The Move Book by the Move community.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/move-code-quality