com um clique
mvx-diff-review
Reviewing changes between versions of SCs (Upgradeability checks).
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Reviewing changes between versions of SCs (Upgradeability checks).
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Guidelines for establishing context before an audit.
Perform a comprehensive on-chain security audit of a deployed MultiversX smart contract. Use when reviewing a contract's security posture, permissions, state, and economic safety without source code.
Read on-chain state in MultiversX smart contracts. Use when accessing caller info, account balances, block timestamps, ESDT token metadata, local roles, code metadata, or any data from self.blockchain().
Gas-optimized cache patterns for MultiversX smart contracts using Drop-based write-back caches. Use when building contracts that read/write multiple storage values per transaction, DeFi protocols, or any gas-sensitive contract.
Identify ambiguous requirements and ask targeted clarifying questions for MultiversX development. Use when user requests are vague, missing technical constraints, or have conflicting requirements.
Comprehensive code analysis toolkit for MultiversX smart contracts. Covers differential review (version comparison, upgrade safety), fix verification (validate patches, regression testing), and variant analysis (find similar bugs across codebase). Use when reviewing PRs, verifying security patches, or hunting for bug variants.
| name | mvx-diff-review |
| description | Reviewing changes between versions of SCs (Upgradeability checks). |
This skill helps you analyze the difference between two versions of a codebase, focusing on security implications of changes.
When reviewing a diff between v1 and v2 of a Smart Contract:
struct stored in a VecMapper or SingleValueMapper change?v2 introduce new Storage Mappers?#[upgrade]? (Remember #[init] is NOT called on upgrade).git diff v1..v2.mvx-code-analysis — Section 1 expands on storage-layout compat, init-on-upgrade, and breaking-change detection.mvx-upgrade-flow — Deployment-side of the same problem (pre/post-upgrade verification).mvx-sc-audit Phase 2 — How differential review plugs into a full audit.