diff_review

Analyzes MultiversX smart contract diffs for upgradeability issues and regressions.

12|5|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/multiversx/mx-ai-skills --skill diff-review-multiversx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff_review
Source: https://github.com/multiversx/mx-ai-skills/tree/main/antigravity/skills/diff_review
Command: npx skills add https://github.com/multiversx/mx-ai-skills --skill diff-review-multiversx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify critical security and functionality risks introduced by changes between two versions of a smart contract codebase, ensuring smooth upgrades.

Core Features & Use Cases

  • Upgradeability Checks: Detects potential storage layout corruption and uninitialized new mappers in upgrade scenarios.
  • Regression Testing: Helps identify if new features break existing invariants or if essential checks have been removed.
  • Use Case: Before deploying a new version of your MultiversX smart contract, use this skill to review the code diff and ensure that storage compatibility is maintained and no critical security checks are missed.

Quick Start

Review the code changes between version 1 and version 2 of the smart contract to identify potential upgradeability issues.

Frequently Asked Questions about diff_review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check MultiversX smart contract upgradeability issues in a code diff?

To check smart contract upgradeability issues, analyze the code diff between contract versions to detect storage layout changes in mappers and uninitialized new storage that could corrupt state during upgrades.

What is smart contract storage layout corruption and how does a diff review detect it?

Storage layout corruption occurs when upgrades alter mapper structures. A diff review detects this by analyzing code differences between contract versions to identify incompatible storage changes and uninitialized mappers.

Can I use a diff review to find removed security checks in my smart contract upgrade?

Yes, a diff review identifies removed security checks by validating that new features do not break existing invariants and ensuring no critical checks are lost during smart contract upgrades.

Does a smart contract diff review work for MultiversX-specific storage mappers?

Yes, smart contract diff review works for MultiversX-specific mappers by detecting storage layout changes and validating the initialization of new mappers during upgrades.

What is the best way to prevent regressions when upgrading MultiversX smart contracts?

The best way to prevent regressions is to review code differences between smart contract versions to identify if new features break existing invariants or if essential checks have been removed.

When do I need to run a smart contract code diff analysis?

You need to run a smart contract code diff analysis before deploying a new version to ensure storage compatibility is maintained, new mappers are initialized, and no critical security checks are missed.