Skip to content

Lint

Validate CODEMANIFEST files in a project.

The lint domain is the structural gate of the DSL. Which tasks it solves:

  • Validate the manifest — goga lint parses every CODEMANIFEST in the project tree and checks it against the rule set: document-level rules (applied per document by the AST visitor) and tree-level rules (applied across the import graph by the analyzer).
  • Report precisely — every error carries the rule name, the message, the document path, and the offending YAML fragment; a closing summary counts cells and errors.
  • Scope the noise — the lint.ignore list prunes directories (a vendored .venv, a build output) from traversal before validation.
  • Explain the failures — the error catalog describes what each rule checks and what a violation means.

What each rule means semantically — the DSL itself — is covered in Cells; how the rules are implemented (the visitor, the analyzer, the error hierarchy) in Cells — AST.

In this directory

  • CLI — the full goga lint command reference
  • Configuration — the lint: section of .goga/config.yml
  • Hooks — hook points for tool packages
  • API — the goga.ast package facade
  • Errors — the catalog of validation errors
  • Error Hierarchy — the error classes the validation pipeline raises
  • Validation Rules — the implementation-side rules reference