workspace-build

Build and test Nx workspace submodules affected by changes.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill workspace-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-build
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/workspace-build
Command: npx skills add https://github.com/open-hax/opencode-skills --skill workspace-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and validate changes across a multi-repo workspace by focusing on affected submodules and running tests for modified areas.

Core Features & Use Cases

  • Selective builds: Detects and builds only the submodules affected by your changes to save time.
  • Automated testing: Runs tests for affected projects to ensure integrity before commit.
  • Fallback option: Provides a full workspace build when necessary to guarantee end-to-end coverage.

Quick Start

Run the workspace-build skill to trigger an affected-submodules build and test cycle across the workspace.

Frequently Asked Questions about workspace-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and test only affected submodules in an Nx workspace?

To build and test affected submodules in an Nx workspace, run the workspace-build skill. It detects modified projects via nx.json and automates builds and tests for affected areas to ensure integrity.

What is the best way to run selective builds for multi-repo workspace changes?

Selective builds for multi-repo workspaces are handled by detecting affected submodules through Nx configuration. This approach focuses on modified areas, saving time by skipping unchanged projects during the build cycle.

Does workspace-build work with git submodules and Nx affected projects?

Yes, workspace-build applies to multi-submodule workspaces and uses Nx to detect affected projects. It requires an nx.json file to identify changes and execute corresponding build and test sweeps.

Can I run a full workspace build if affected project detection fails?

Yes, if affected project detection is insufficient, a fallback option provides a full workspace build. This guarantees end-to-end build and test coverage across all submodules when necessary.

Why do I need an nx.json file for testing affected workspace submodules?

An nx.json file is needed for testing affected workspace submodules because it provides the configuration required to detect which projects have changes. This enables targeted automated testing before commit.