BSK-0003 analyze

Missing variable type annotation

Fires when a module-level variable has no type annotation. This house rule is off by default — the default configuration is pure PEP conformance — and a project opts in via configuration. When enabled, every module-level binding must carry an explicit annotation so that Basilisk can verify downstream usage and generate accurate stubs.

Real basilisk check output

What you see when BSK-0003 fires on a minimal example:

basilisk check output reporting BSK-0003 — Missing variable type annotation

How to handle it

This Basilisk-specific rule is off by default. Enable its strictness tag when the policy fits your project, then configure its severity globally or per path in pyproject.toml.

Canonical URL: https://www.basilisk-python.dev/errors/BSK-0003