verify-maps

Verify Python code maps against generated symbol tables before code generation.

37|5|Updated Nov 18, 2025

Search Tags:#static analysis #code generation #verification #type checking #maps

Ready to run

npx skills add https://github.com/BellaBe/lean-os --skill verify-maps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-maps
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/engineering-verify-maps
Command: npx skills add https://github.com/BellaBe/lean-os --skill verify-maps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill static analyzes code maps to catch type mismatches, wrong arguments, and missing imports before code generation, delivering a fast-feedback loop.

Core Features & Use Cases

Symbol table construction: extract types, protocols, and data models.
Call-site verification: ensure calls match domain definitions.
Early error detection: surface mismatches prior to codegen.

Quick Start

Example: "Validate 100 code-map calls against domain types in artifacts/v1/gen/maps/*.map.yaml."

Frequently Asked Questions about verify-maps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify code maps against type definitions before code generation?▼

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.

What errors can static analysis catch in Python code maps?▼

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.

Can I verify maps for domain types, effects, and interfaces?▼

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.

When should I use map verification in my code generation workflow?▼

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.

What output does map verification produce?▼

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.

Do I need existing type definitions to verify code maps?▼

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.