Skip to Content

check

The check tool validates a project against the Manh framework conventions, from syntax to TypeScript types, and returns each error with its file, line and fix; deploys are refused while it reports errors.

check

Runs the check layers on the project’s current file tree. It writes nothing.

  • Parameters:
    • project.
    • typecheck: true also runs full TypeScript, which takes about 5–15 seconds. Default false.
  • Returns: errors and warnings, one per line with the layer, rule id, file, line and an explanation; then the Progress section and a next step.
  • When the agent calls it: at the end of each phase with typecheck: true, not after every file.
✗ 1 error(s) Errors: - [gate:code.antd-v6-no-visible-prop] app/orders/page.tsx:42 <Modal visible={…}> — antd v6 Modal ignores `visible` … Warnings: - [gate:perf.order-unindexed] app/orders/repository.ts:18 orders.createdAt is used in orderBy but …

Layers

  1. Syntax: parses every .ts and .tsx file.
  2. Gates: code patterns that crash the app or leave the stack.
  3. Contract: the route tree, UI calls that match a real API, the .ts / .tsx boundary, Drizzle usage.
  4. Types: TypeScript over the app’s code, only with typecheck: true.

write_files and block_add run the first three layers and return the result in the same call. deploy runs all four.

Errors and warnings

  • Errors block a deploy. Only type errors and page render errors can be overridden, with deploy({ force: true, reason }).
  • Warnings don’t block a deploy, but they usually point at places where the app does not yet feel like a real product: a missing index, a feature block not wired up, placeholder data.

Next steps

  • check rules: the main rules by group.
  • deploy: how check runs on deploy.
  • Files: the check result after each write.
Last updated