assist verify and assist lint

assist verify runs a repo’s checks; see Verify.

Commands

• assist verify list lists the repo’s verify:* checks.
• assist lint checks TypeScript conventions that oxlint doesn’t: file names match what they export (PascalCase only for classes and components), imports are static, and relative imports have no file extension. -f renames misnamed files and updates their imports.
• assist coverage runs the Vitest tests with coverage and prints the overall statement coverage percentage.

Built-in checks

These are ready-made checks to add as verify:* run commands, such as assist run add verify:no-venv assist verify no-venv.

• assist verify hardcoded-colors fails on hex colours in src/, so colours come from the theme. Exempt files with hardcodedColors.ignore:

  assist config set hardcodedColors.ignore "**/theme.ts"

• assist verify block-code-comments fails on any code comment on a changed line. Exempt files with blockCodeComments.ignore:

  assist config set blockCodeComments.ignore "**/*.test.ts"

• assist verify no-venv fails when the repo contains a Python venv folder.

• assist verify forbidden-strings fails when a value in a JSON file matches a disallowed glob. Each forbiddenStrings rule names a file, the dotted paths to read in it, and the disallowed glob:

  forbiddenStrings:
    - file: appsettings.json
      paths:
        - ConnectionStrings.Default
      disallowed: "*Password=*"

• assist verify migrations fails when database migrations aren’t numbered in sequence, when an existing migration was edited, or when one drops data without an acknowledgement marker.

Checks for the assist repo

assist verify config-keys and assist verify advice-fragments check assist’s own source: that every config key is documented in some command’s --help, and that every shipped repo instructions fragment can be named in advice.sections.