sui-publish

What problem does it solve?

Publishing, upgrading, and deploying Sui Move packages is error-prone because you must coordinate the right CLI commands, environment/network selection, UpgradeCap handling, and dry-run debugging so changes are compatible and production-safe.

Core Features & Use Cases

• First-time publishing & pre-publish validation: Verify active environment, SUI balance, and successful sui move build before running sui client publish.
• Upgrading with UpgradeCap + policies: Apply sui client upgrade using the correct UpgradeCap, select the appropriate upgrade policy (compatible/additive/dependency-only), and optionally restrict or destroy the cap for immutability.
• Multi-network deployment + offline/local workflows: Publish to Testnet/Devnet/localnet with environment switching, use ephemeral test-publish for upgrades/testing, and use localnet for fast iteration.
• Production readiness + transaction debugging: Use --dry-run for gas estimation and devInspectTransactionBlock to diagnose dry-run failures before signing or executing.

Quick Start

Ask the skill to publish your Move package by first verifying your active environment and build, then running sui client publish and returning the package ID, UpgradeCap, and any init-created object IDs.