nx-run-tasks

Execute build, test, and lint tasks within an Nx workspace.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/guysenpai/crustacean --skill nx-run-tasks-guysenpai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-run-tasks
Source: https://github.com/guysenpai/crustacean/tree/main/.gemini/skills/nx-run-tasks
Command: npx skills add https://github.com/guysenpai/crustacean --skill nx-run-tasks-guysenpai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the execution of development tasks within an Nx monorepo, ensuring consistency and efficiency across build, test, and linting operations.

Core Features & Use Cases

  • Task Execution: Run single or multiple Nx tasks across projects.
  • Affected Commands: Optimize CI/CD pipelines by running tasks only on changed projects.
  • Use Case: When a developer needs to build and test all projects affected by recent changes in a large Nx workspace, this skill provides the commands to do so efficiently.

Quick Start

Run the build and test tasks for all projects affected by recent code changes.

Frequently Asked Questions about nx-run-tasks

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

FAQPage Schema
How do I run build and test tasks only for projects affected by recent code changes in an Nx monorepo?

You can run tasks for affected projects in an Nx workspace by utilizing affected commands, which analyze code changes and execute build or test operations only on the impacted projects to optimize your workflow.

What is the best way to execute multiple tasks across different projects in an Nx workspace?

Executing multiple tasks across an Nx workspace is handled by running single or multiple task commands, providing options for caching, verbosity, and parallel execution to ensure efficient task completion across projects.

Can I use parallel execution and caching when running lint tasks in an Nx workspace?

Yes, executing lint tasks in an Nx workspace supports configuration options for caching, verbosity, and parallel execution to streamline the linting process and improve performance.

How do I optimize CI/CD pipelines for an Nx monorepo using affected commands?

You can optimize CI/CD pipelines in an Nx monorepo by running affected commands, which execute build, test, and lint tasks solely on projects affected by recent changes rather than the entire workspace.

Does running Nx workspace tasks require configuring specific dependencies before execution?

Running Nx workspace tasks does not require configuring specific external dependencies, as the skill directly executes build, test, and lint operations within the existing workspace environment.

Why run tasks only on affected projects instead of the entire Nx workspace?

Running tasks on affected projects optimizes execution time and resources by targeting only changed projects, ensuring consistency and efficiency across build, test, and linting operations in large workspaces.