メニュー
Verifying if a reported bug is truly fixed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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-fix-verification |
| description | Verifying if a reported bug is truly fixed. |
This skill helps you rigorous verify that a reported vulnerability has been eliminated without introducing regressions.
mandos scenario that fails (demonstrates the bug).deposit but not transfer).A "Verification Report" stating:
ScenarioWorld; .scen.json scenarios are still accepted).mvx-code-analysis — Fix verification as Section 2 with worked examples (exploit scenario JSON + recommendation template).mvx-variant-analysis — Run after any verified fix to find similar bugs elsewhere.mvx-testing-handbook — Writing the blackbox test used to lock the fix in.