nx-run-tasks

Name: nx-run-tasks
Availability: InStock
Author: TheCardGoat

Execute Nx build, test, lint, typecheck, and serve tasks in a monorepo.

14|5|Updated Mar 16, 2026

Search Tags:#testing #build #task runner #monorepo #nx #ci #affected projects

Ready to run

npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill nx-run-tasks-thecardgoat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nx-run-tasks
Source: https://github.com/TheCardGoat/lorcana-simulator/tree/main/.opencode/skills/nx-run-tasks
Command: npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill nx-run-tasks-thecardgoat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly execute the correct build, test, lint, typecheck, or serve tasks in an Nx monorepo without guessing project names or target names.

Core Features & Use Cases

Discover runnable Nx targets: Identify which projects and targets exist using Nx introspection (including inferred tasks).
Run single or multiple tasks: Execute one target for a project or run many targets across projects.
Focus on affected projects: Limit work to changed and dependent projects to speed up local development and CI.

Quick Start

Run the command you need in your terminal by using nx run <project>:<task> for a single target or nx run-many -t <task1> <task2> to run multiple tasks across the workspace.

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, test, and lint tasks across an Nx monorepo without manually checking project names?▼

To run build, test, and lint tasks across an Nx monorepo, use `nx run-many -t <task1> <task2>` to execute multiple targets across the workspace without manual target discovery. It automatically identifies available projects.

How do I only run tests for projects affected by my recent code changes in an Nx workspace?▼

Run tests for affected projects in an Nx workspace by using the `nx affected` command with common filtering flags. This limits execution to changed and dependent projects, speeding up local development and CI pipelines.

How can I discover runnable target names for a specific project in an Nx monorepo?▼

Discover runnable target names for a specific project in an Nx monorepo using the `nx show project` command. This introspection tool identifies all available targets, including inferred tasks, for accurate selection.

What is the best way to execute a single build task for one project in an Nx workspace?▼

The best way to execute a single build task for one project in an Nx workspace is using the `nx run <project>:<task>` command. This ensures accurate target selection without guessing project names.

Do I need to manually configure CI pipelines to use Nx affected commands for incremental builds?▼

No, you do not need to manually configure CI pipelines to use Nx affected commands. The Skill applies to CI pipelines and workspace-wide automation, enabling affected-only execution natively through standard Nx command usage.

Why does Nx run-many fail to execute typecheck tasks across all my workspace projects?▼

If `nx run-many` fails to execute typecheck tasks, it is often due to inaccurate target discovery. Ensure the typecheck target exists for your projects by verifying available targets with `nx show project` before running multi-target execution.