nx-run-tasks

Automate Nx target execution across multiple projects from one command.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nx task runner orchestration often requires manually invoking multiple commands for single or multi-project builds, tests, and linting, which slows developer workflow.

Core Features & Use Cases

  • Run a single Nx target: nx run <project>:<task>.
  • Run multiple targets across projects: nx run-many -t build test lint.
  • Discover available targets and plugins from project.json/package.json metadata to plan work.

Quick Start

Run a single task with nx run <project>:<task> or run multiple tasks with nx run-many for a group of projects.

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 multiple Nx targets across different projects in a workspace?

To run multiple Nx targets across projects, use the nx run-many -t command followed by the desired tasks like build, test, and lint. This automates executing multiple project targets from a single command within your Nx workspace.

Can I use pnpm or yarn prefixes to execute Nx tasks?

Yes, you can execute Nx tasks using optional prefixes like npx, pnpx, or yarn. The task runner relies on Nx CLI conventions while supporting these package manager prefixes to invoke targets defined in your workspace.

How do I execute a single build or test target for a specific Nx project?

To execute a single build or test target for a specific project, use the nx run command with the project and task name syntax. This reads your project configuration from package.json or project.json to run the specified task.

What is the best way to discover available Nx targets and plugins in my workspace?

The best way to discover available targets and plugins is by reading project.json or package.json metadata. This allows you to identify defined build, test, lint, and serve tasks to plan your workspace automation work effectively.

Does this Nx task runner work with targets defined in both package.json and project.json?

Yes, the Nx task runner works with targets defined in both package.json and project.json files. It reads project targets from either metadata file to automate running build, test, lint, and serve tasks across your workspace.

Why should I use a single command to run Nx tasks instead of invoking them manually?

Using a single command to run Nx tasks eliminates manually invoking multiple commands for multi-project builds, tests, and linting. This orchestration speeds up your developer workflow by automating target execution across the workspace.