How do I install the Nx Run Tasks skill?

Run npx skillmds@latest add gabrielmoreira/nx-run-tasks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nx Run Tasks safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nx Run Tasks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nx Run Tasks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nx Run Tasks?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nx Run Tasks by gabrielmoreira — Agent Skill

Name: Nx Run Tasks
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Nx Run Tasks

Execute build, test, lint, serve, and other tasks in an Nx workspace using single runs, run-many, and affected commands. Use when user says "run tests", "build my app", "lint affected", "serve the project", "run all tasks", or "nx affected". Do NOT use for code generation (use nx-generate) or workspace configuration (use nx-workspace).

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

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)

---name: nx-run-tasksdescription: Execute build, test, lint, serve, and other tasks in an Nx workspace using single runs, run-many, and affected commands. Use when user says "run tests", "build my app", "lint affected", "serve the project", "run all tasks", or "nx affected". Do NOT use for code generation (use nx-generate) or workspace configuration (use nx-workspace).--- 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`)

Frequently asked questions