insight-storm

Adversarial code review on a git diff identifies failure modes and assumption conflicts by analyzing irreversible decisions and partial state conditions. It detects naming mismatches and enforces project values across modules before merging critical features.

Adversarial testing for failure modes evaluates how code handles incomplete data states by checking implicit assumptions and irreversible decisions. It proactively detects inconsistencies to prevent complex transaction logic from leaving data in an invalid state.

Checking cross-module consistency involves scanning code changes for naming mismatches and assumption conflicts across modules. It enforces project-defined values and identifies implementation inconsistencies to ensure coherent integration before deployment.

Automated risk assessment identifies irreversible decisions and implicit assumptions in code changes. It analyzes inputs and outputs under partial state conditions to proactively surface failure modes and assumption conflicts before they impact production.

Adversarial code review focuses on logic, consistency, and risk assessment but does not execute code. It relies on analyzing the git diff to find assumption conflicts and naming mismatches, meaning it complements but does not replace runtime testing.

Yes, the insight-storm skill processes standard git diff output to perform consistency checks and adversarial code review. It analyzes the provided changes to identify failure modes, enforce project values, and detect cross-module inconsistencies.