gxpm-build

Catch TypeScript build and type errors before committing by running a build verification command like bun run check on your code changes. This surfaces the first root cause of compilation failures early and records exit codes for local traceability.

Identify the root cause of a gxpm compilation failure by enforcing a type-check execution on your project. The skill surfaces the first root cause of the failure, preventing post-change surprises when builds fail and root causes are unclear.

Run a pre-verify type-check step in a gxpm workflow by applying the build verification process to code changes before commits. Execute a command such as bun run check to maintain code health and validate that changes compile successfully.

Yes, build verification records exit codes and results for audit-friendly debugging and traceability. When you enforce execution of a build or type-check command, the skill logs the output locally to help track down compilation failures.

Run type-checks on code changes before they are committed to prevent post-change surprises. Validating that code compiles and passes type checks in pre-verify steps surfaces the first root cause of failures early, maintaining overall code health.

Yes, you can use bun run check for build verification in a TypeScript project. Enforcing this build and type-check command validates compilation, surfaces the first root cause of any failures, and records the exit codes for traceability.