Analysis and debugging

Inspect a contract#

Review built-in correctness, security, gas, naming, and ERC-related checks. Configure Solhint or Slither when your project uses those tools and compare their output with the plugin’s native inspections.

Use the Solidity Audit tool window for audit tooling and Solidity Storage for storage-layout analysis. Check compiler version and contract selection before comparing outputs, especially when reviewing an upgradeable contract’s layout.

Debug execution#

Configure the supported DAP workflow with a compatible adapter and a launch configuration for the intended runtime. First confirm the framework can compile and execute the test or program normally. Then set breakpoints and start debugging.

Inspect stack and values when paused and verify that the source matches the compiled artifacts. Adapter startup errors should be resolved in adapter configuration rather than by changing unrelated inspections.

Import or verify deployed code#

Use Etherscan-related actions for importing, flattening, and verification when needed. Confirm chain, address, compiler version, optimization options, and credentials. Review flattened output before distributing it; imported or generated code still needs your normal review and tests.