Add Sui Move support to develop-secure-contracts#11
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Extends the existing develop-secure-contracts skill to cover Sui Move integration using the same “pattern discovery from installed dependency source + docs/examples” methodology used for other ecosystems.
Changes:
- Adds
.moveto the project contract-file search globs. - Documents Sui Move dependency resolution via
Move.toml+ MVR and local doc generation viasui move build --doc. - Adds Sui Move to the repository/documentation lookup table and introduces a Sui-specific integration notes section emphasizing examples/metadata-driven discovery.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
0xNeshi
approved these changes
Jul 8, 2026
ericglau
requested changes
Jul 14, 2026
Extend the cross-ecosystem develop-secure-contracts skill with Sui Move, delivering the library-integration capability for Sui (no separate skill, consistent with the other ecosystems). - detect `.move` in the project file-glob search - resolve dependencies from Move.toml `r.mvr` (source under ~/.move/ and the build mirror; `sui move build --doc` for code docs) - add a Sui Move row to the repository/documentation lookup table - note that Sui is deliberately not in the fixed category grid — discover its package set from llms.txt -> catalogs -> package READMEs/examples - add a Sui Move Integration Notes section: no CLI generator (use pattern discovery + examples), and route conventions to their sources of truth (ARCHITECTURE.md, STYLEGUIDE.md, package README, docs site / API reference, and the setup-sui-contracts skill) rather than restating them Methodology-first and discovery-driven: specifics that drift (slugs, module lists, patterns) are read from the library's own metadata, not hardcoded.
Address PR review: make the Sui dependency-source and code-docs locations precise and consistent with setup-sui-contracts — read exact signatures from build/<pkg>/sources/dependencies/<move_package_name>/, and note dependency docs land under build/<pkg>/docs/dependencies/<move_package_name>/.
…ate before finishing - Use `--build-env <env>` (required whenever there are MVR deps) rather than enumerating `testnet|mainnet` (PR review). - Note to run the project's full quality gate (build, test, prettier-move, lint) before finishing.
…rmatter to SSOT Address PR review: - Disambiguate `<pkg>`: use `<move_package_name>` for the Move.toml dependency key and `<project_package>` for the `build/.../` output directory. - Quality-gate note no longer names a formatter; defer the exact commands and formatter to the setup-sui-contracts skill (single source of truth) instead of restating them.
…s link Address PR review: drop the ambiguous `.../<major>.x/api/<package>` path (the URL segment isn't the Move package name); route to the canonical API reference through each package's catalog `Docs` link instead.
Fresh-subagent case: integrate OZ RBAC into an existing Sui Move module — verifies discovery from library metadata/examples (no CLI generator), import via MVR (not copy), and reading installed dependency source for signatures.
bidzyyys
force-pushed
the
feat/develop-secure-sui
branch
from
July 15, 2026 09:47
8c42f12 to
2641623
Compare
…xt pointer Addresses review feedback that the Sui-specific notes were too verbose for a shared multi-ecosystem skill and polluted context for non-Sui readers. Replace the "Sui Move Integration Notes" section and the grid paragraph with one concise note that routes to llms.txt (the single entry point) + the setup-sui-contracts skill, and trim the Step 1 dependency-location bullet to match its peers.
… 3.6 The example omitted `--build-env`, which fails on MVR deps. The develop-secure pattern-discovery path reads the installed source via the build mirror; the `--doc` generation flow belongs to the setup-sui-contracts skill, so don't duplicate it here.
Genericize the concrete `@openzeppelin-move/access` slug to the `@openzeppelin-move/<slug>` placeholder form used elsewhere in the skills, so the scenario doesn't pin a specific registry slug that could drift.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends the cross-ecosystem
develop-secure-contractsskill with Sui Move, delivering the library-integration capability for Sui (consistent with the other ecosystems — no separate skill).What it adds
.movedetection in the project file-glob search.Move.tomlr.mvr(installed source under~/.move/+ the build mirror;sui move build --docfor code docs).llms.txt→ the package catalogs → each package'sREADME.md/examples/.examples/), and route conventions to their sources of truth —ARCHITECTURE.md(capability-based access, owned/shared objects),STYLEGUIDE.md(Move 2024 idioms), the packageREADME.md(exactr.mvrsnippet +usepath), the docs site / API reference (signatures/params/aborts), and thesetup-sui-contractsskill (toolchain,Move.toml, dependency-conflictoverride, builds, testing) — rather than restating them.Methodology-first and discovery-driven: anything that drifts (slugs, module lists, patterns) is read from the library's own metadata, not hardcoded.
Notes
feat/setup-sui-contracts(PR Add setup-sui-contracts skill #10) for the shared Sui context; retarget tomainafter that merges.