convex-typecheck-guard

Automate Convex type checking by running a guard process that executes `pnpm convex typecheck` automatically whenever files under the `convex/` directory are modified. This enforces code integrity during development.

Run Convex type checks after any backend edit, including schema changes, permission updates, migrations, queries, or mutations, and always before commit, push, or final handoff to catch errors early.

You need a Convex environment capable of parsing and executing type checking scripts, along with the `pnpm` package manager to run the `convex typecheck` command on your codebase.

Yes, executing `pnpm convex typecheck` after modifying files in the `convex/` directory serves as pre-commit safety to catch potential schema and type errors early in the development cycle.

Yes, this type checking process works with any Convex backend edit, covering schema changes, permission updates, migrations, queries, mutations, actions, and generated API-affecting changes.

Convex type checking fails on file changes when modifications under the `convex/` directory introduce type errors or schema inconsistencies, which the `pnpm convex typecheck` script detects during validation.