nx-run-tasks

Execute build, test, and lint tasks across Nx monorepo workspaces.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill nx-run-tasks-wahidyankf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-run-tasks
Source: https://github.com/wahidyankf/ose-primer/tree/main/.opencode/skills/nx-run-tasks
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill nx-run-tasks-wahidyankf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and manual effort of running tasks across Nx monorepo projects, saving developers time and reducing configuration errors when executing build, test, lint, and other workspace operations.

Core Features & Use Cases

  • Target Discovery: Automatically list all runnable tasks for any Nx project, including inferred targets from Nx plugins, without manually parsing configuration files.
  • Flexible Task Execution: Run single or multiple tasks across all projects, filtered project sets, or only affected projects for continuous integration efficiency.
  • Use Case: A developer modifying a shared library can run lint and test tasks only for dependent apps instead of the entire monorepo, cutting down local and CI execution time.

Quick Start

Use the nx-run-tasks skill to run the build and test tasks for all projects affected by your 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 affected projects in an Nx monorepo?

To run tasks for affected projects in an Nx monorepo, you can target only the projects impacted by recent code changes. This approach cuts down local and continuous integration execution time by skipping unaffected workspace operations.

How do I discover all runnable targets for an Nx project without parsing configuration files?

You can discover runnable targets for an Nx project through automatic target discovery. This mechanism lists all defined tasks, including those inferred from Nx plugins, eliminating the need to manually parse configuration files.

What is the best way to execute lint and test tasks across a filtered set of Nx projects?

The best way to execute tasks across a filtered set of Nx projects is by using flexible task execution. This provides the correct Nx command syntax and flag usage to run single or multiple operations across specific project sets.

Can I run multiple workspace operations across all projects in an Nx monorepo simultaneously?

Yes, you can run multiple workspace operations across all Nx monorepo projects simultaneously. The automation provides correct command syntax to execute tasks like build, test, and lint across the entire workspace configuration.

Why use affected project filtering for continuous integration workflows in an Nx workspace?

Using affected project filtering for continuous integration in an Nx workspace reduces execution time. It runs tasks only for projects dependent on recent changes, eliminating manual configuration lookup and reducing continuous integration overhead.