verify-maps

Verify maps by building a symbol table from generated type files, then validating each call and field access in your code maps against that table. The Skill checks for type mismatches, wrong arguments, and missing imports, reporting errors to artifacts/v{N}/gen/maps-verification.yaml with exit code 1 on failure.

Static analysis detects type mismatches between map calls and domain definitions, incorrect function arguments, missing imports, and invalid field accesses. It surfaces these errors before code generation runs, enabling fast feedback on 100+ code-map calls in a single pass.

Yes. The Skill validates Python code maps produced for domain types, effects, and interfaces by checking every call and field access against the constructed symbol table, ensuring consistency across all three code-map categories.

Use map verification as an early-stage gate before code generation to prevent invalid maps from reaching downstream tooling. It's essential when working with generated type files and domain models where type safety and correctness are prerequisites for successful code generation.

Map verification generates a detailed report written to artifacts/v{N}/gen/maps-verification.yaml, documenting all validation results. The Skill exits with code 0 on success and code 1 if any type mismatches, argument errors, or missing imports are found.

Yes. Map verification requires generated type files to build its symbol table. You must have domain type definitions, effect types, and interface definitions already available in your artifacts directory for the Skill to validate code maps against them.