nx-run-tasks

A repository holding dozens of projects takes far too long to build end to end; this runs just the part you asked for, or just the part your latest change could have broken.

WHEN TO USE

SCOPE

USE FOR

Run a single task, like build or test, for one named project.
Run the same task across every project in the workspace at once.
Run tasks only for the projects a code change actually affected, to save time in CI.
Check which tasks are defined for a specific project before running one.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (5)

You can run tasks with Nx in the following way.

Keep in mind that you might have to prefix things with npx/pnpx/yarn if the user doesn't have nx installed globally. Look at the package.json or lockfile to determine which package manager is in use.

For more details on any command, run it with --help (e.g. nx run-many --help, nx affected --help).

Understand which tasks can be run

You can check those via nx show project <projectname> --json, for example nx show project myapp --json. It contains a targets section which has information about targets that can be run. You can also just look at the package.json scripts or project.json targets, but you might miss out on inferred tasks by Nx plugins.

Run a single task

nx run <project>:<task>

where project is the project name defined in package.json or project.json (if present).

Run multiple tasks

nx run-many -t build test lint typecheck

You can pass a -p flag to filter to specific projects, otherwise it runs on all projects. You can also use --exclude to exclude projects, and --parallel to control the number of parallel processes (default is 3).

Examples:

nx run-many -t test -p proj1 proj2 — test specific projects
nx run-many -t test --projects=*-app --exclude=excluded-app — test projects matching a pattern
nx run-many -t test --projects=tag:api-* — test projects by tag

Run tasks for affected projects

Use nx affected to only run tasks on projects that have been changed and projects that depend on changed projects. This is especially useful in CI and for large workspaces.

nx affected -t build test lint

By default it compares against the base branch. You can customize this:

nx affected -t test --base=main --head=HEAD — compare against a specific base and head
nx affected -t test --files=libs/mylib/src/index.ts — specify changed files directly

Useful flags

These flags work with run, run-many, and affected:

--skipNxCache — rerun tasks even when results are cached
--verbose — print additional information such as stack traces
--nxBail — stop execution after the first failed task
--configuration=<name> — use a specific configuration (e.g. production)

Local tool required

1 FOR YOU

01
Have an existing Nx workspace
Have Node.js and an existing Nx workspace with the nx CLI (via npx/pnpx/yarn if not installed globally) so nx run, nx run-many, and nx affected can execute tasks.

This skill ships inside the Nx AI Agent Skills plugin. Listed package contents include 1 agent. Installed components and skill versions may vary by AI tool.

Install just this skill

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add nrwl/nx-ai-agents-config --skill "nx-run-tasks" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

Install the whole plugin

This route installs the Nx AI Agent Skills plugin package selected for your AI tool.

PLUGIN MARKETPLACE

Add the marketplace, then install the plugin

Typed inside the agent's own prompt, not in a terminal. The marketplace is called nx-claude-plugins, which is the part after the @.

/plugin marketplace add nrwl/nx-ai-agents-config

02
```
/plugin install nx@nx-claude-plugins
```

Open plugin page ↗

View on GitHub

Understand which tasks can be run

Run a single task

Run multiple tasks

Run tasks for affected projects

Useful flags

Local tool required

Install just this skill

Install the whole plugin

Add the marketplace, then install the plugin

More skills

link-workspace-packages

monitor-ci

nx-cloud-api

nx-cloud-cache-investigator

nx-cloud-ci-failure-review

nx-generate