القائمة
Bump the pinned Sui version everywhere it lives, per dev-docs/conventions/sui-version-bump.md. Usage - /bump-sui mainnet-v1.71.0 (or a testnet-v tag).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guide for operating Ika network nodes - validators, fullnodes, and notifiers. Use when deploying, configuring, monitoring, or troubleshooting Ika infrastructure. Triggers on tasks involving ika-node, ika-validator, ika-fullnode, ika-notifier, NodeConfig, consensus setup, P2P networking, validator registration, or Ika node operations.
Validate that an expensive integration/upgrade test actually catches the failure it claims to — by injecting a minimal, targeted fault and confirming the EXPECTED evidence appears in the logs, then reverting. Guards against tests that pass vacuously. Key idea most people miss: the injected failure is often RECOVERABLE (the system detects and excludes it and the test still PASSES), so the log evidence — not the exit code — is the real assertion. Use before trusting a green cross_binary / v118 / cluster run as proof of wire/state compatibility or malicious-party detection.
Dispatch the heavy CI test suites (Rust integration, cluster, TypeScript) on a branch and watch them to verdicts. Use when a branch needs full validation before merge.
Ordered diagnosis for "MPC stopped making progress" — wedged epochs, cascading SDK timeouts, quorum silence. Runs the dev-docs playbook checks against a localnet/validator log.
Guide for using the Ika CLI tool for dWallet operations, validator management, system deployment, and network administration. Use when performing CLI-based dWallet creation, signing, presigning, key management, validator operations, system initialization, or querying Ika network state via the terminal. Triggers on tasks involving `ika` CLI commands, dWallet CLI operations, Ika system deployment, or MCP tool integration with Ika.
Guide for integrating Ika dWallet 2PC-MPC protocol into Sui Move contracts. Use when building Move contracts that need cross-chain signing, dWallet creation, presigning, signing, future signing, key importing, or any Ika on-chain integration. Triggers on Move/Sui contract tasks involving dWallets, cross-chain signing, or Ika protocol operations.
| name | bump-sui |
| description | Bump the pinned Sui version everywhere it lives, per dev-docs/conventions/sui-version-bump.md. Usage - /bump-sui mainnet-v1.71.0 (or a testnet-v tag). |
| user-invocable | true |
| disable-model-invocation | true |
Bump the Sui pin to $ARGUMENTS (a mainnet-vX.Y.Z or testnet-vX.Y.Z
tag). Full checklist: dev-docs/conventions/sui-version-bump.md. Work
on a dedicated branch.
Cargo.toml.Cargo.toml pin (~90 occurrences, one sed),
then cargo update.(cd sdk/ika-wasm && cargo update) (and any
other excluded package with its own lock)..github/workflows/ts-integration-tests.yaml and
.github/workflows/ts-ci.yaml, and the pinned-version gotcha in
CLAUDE.md.msim rev's; if they differ, the
[patch.crates-io.tokio] silently no-ops — find an msim rev shipping
the matching tokio../scripts/check-sui-version-consistency.sh (CI enforces it),
then cargo build --release, then dispatch the integration suite
(/dispatch-suites) — crypto and consensus layers are the usual
cross-version breakage points. Watch for #[cfg(msim)] rot
(unresolved import under --cfg msim).sui
binary — a mismatched localnet binary completes DKG but silently
stalls reconfiguration (dev-docs/playbooks/localnet.md).