nx-verify

Run typecheck, lint, and test targets sequentially for Nx projects.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/ViewableGravy/better-ecs --skill nx-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-verify
Source: https://github.com/ViewableGravy/better-ecs/tree/main/.github/skills/nx-verify
Command: npx skills add https://github.com/ViewableGravy/better-ecs --skill nx-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a consistent and reliable way to run essential quality checks (typechecking, linting, and testing) across specified Nx projects, ensuring code quality before commits or handoffs.

Core Features & Use Cases

  • Automated Verification: Runs typecheck, lint, and test targets sequentially for selected Nx projects.
  • Static Output: Ensures terminal output is consistent and easy to parse.
  • Early Failure Detection: Stops execution on the first encountered error, preventing further issues.
  • Use Case: After making changes to the engine and client packages, run this skill to verify that both projects pass all quality gates before pushing your code.

Quick Start

Run verification for the engine and client projects.

Frequently Asked Questions about nx-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run typecheck, lint, and test targets sequentially for Nx projects?

To run typecheck, lint, and test targets sequentially for Nx projects, execute the verification skill. It processes specified projects in order and provides static terminal output for consistent parsing.

What is the best way to verify code quality across multiple Nx packages before a commit?

The best way to verify code quality across multiple Nx packages is running automated verification sequentially. It stops on the first encountered error, ensuring early failure detection before you commit or push code.

Does Nx verification stop execution when a linting or typechecking error occurs?

Yes, Nx verification stops execution when a linting or typechecking error occurs. It runs quality gates sequentially and exits immediately with a non-zero code upon the first failure to prevent further issues.

Can I use this verification flow for my CI/CD pipeline with static terminal output?

Yes, you can use this verification flow for your CI/CD pipeline with static terminal output. It ensures consistent, easy-to-parse logs and exits with a non-zero code upon failure, providing a robust CI/CD verification flow.

Why does my Nx project verification exit with a non-zero code?

Your Nx project verification exits with a non-zero code because a quality gate failed. The skill stops execution on the first encountered error during typechecking, linting, or testing, returning a non-zero exit code to signal the failure.