| name | mvx-fix-verification |
| description | Verifying if a reported bug is truly fixed. |
Fix Verification
This skill helps you rigorous verify that a reported vulnerability has been eliminated without introducing regressions.
1. The Verification Loop
- Reproduce: Create a
mandos scenario that fails (demonstrates the bug).
- Apply Fix: Modification to Rust code.
- Verify: Run the failing mandos. It MUST pass now.
- Regression Check: Run ALL other mandos. They MUST still pass.
2. Common Fix Failures
- Partial Fix: Fixing one path but missing a variant (e.g., fixed
deposit but not transfer).
- Moved Bug: The fix prevents the exploit but creates a DoS vector (e.g., adding a lock that never unlocks).
3. Deliverable
A "Verification Report" stating:
- Commit ID of the fix.
- Test case used to verify (prefer a Rust blackbox test using
ScenarioWorld; .scen.json scenarios are still accepted).
- Confirmation of regression suite success.
See also
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.