skills.rest
patricio0312rev
patricio0312revCOMMUNITY
Explore all skills by this author →
Website𝕏@patricio0312revGitHub

monorepo-ci-optimizer

Detect affected packages and run selective builds and tests in monorepos.

5|Updated Dec 31, 2025
Search Tags:#monorepo#ci-cd#turborepo#nx#affected-detection#incremental-builds
One-click install
npx skills add https://github.com/patricio0312rev/skillset --skill monorepo-ci-optimizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monorepo-ci-optimizer
Source: https://github.com/patricio0312rev/skillset/tree/main/templates/ci-cd/monorepo-ci-optimizer
Command: npx skills add https://github.com/patricio0312rev/skillset --skill monorepo-ci-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monorepos often suffer from lengthy CI times because changes require building and testing many projects. This skill detects which packages or apps are affected by a change and runs only the necessary builds and tests, dramatically reducing CI duration.

Core Features & Use Cases

  • Affected detection with Turborepo or Nx strategies to identify impacted projects
  • Remote caching and parallel execution to accelerate CI runs
  • Matrix-based orchestration to scale across multiple workflows and jobs
  • Use Case: in a large monorepo, a small change to a shared library triggers only the dependent packages to rebuild and test

Quick Start

Configure your CI workflow to run the optimizer and execute only the affected package builds and tests.

Frequently Asked Questions about monorepo-ci-optimizer

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

FAQPage Schema
How do I speed up monorepo CI by building only affected packages?▼

Speed up monorepo CI by detecting affected packages and executing only the necessary builds and tests. This approach reduces CI duration by running tasks exclusively for projects impacted by a change.

What is affected detection in Turborepo and Nx for incremental builds?▼

Affected detection in Turborepo and Nx identifies which packages or apps are impacted by a code change. It enables incremental builds by orchestrating selective tasks and caching to run only necessary workflows.

Does monorepo CI selective testing work with large codebases containing multiple packages?▼

Monorepo CI selective testing works for large codebases with multiple packages. It detects impacted projects and uses remote caching and parallel execution to accelerate CI runs and ensure resource efficiency.

How do I configure CI workflows to run only affected package builds and tests?▼

Configure your CI workflow to run the optimizer and execute only the affected package builds and tests. It uses matrix-based orchestration to scale selective tasks across multiple workflows and jobs.

Do I need Turborepo and Nx to orchestrate selective builds in a monorepo?▼

Yes, you need Turborepo and Nx to orchestrate selective builds and caching. These tools provide the affected detection strategies required to identify impacted projects and execute incremental builds efficiently.

Why does my small change to a shared library trigger full monorepo rebuilds?▼

A small change triggers full rebuilds when CI is not configured for affected detection. By applying selective builds, only the dependent packages of the shared library will rebuild and test, reducing CI duration.

Related Skills

Explore More Software Engineering Skills→
vecearvecear

monorepo-ci-optimizer

Detect affected packages and run only necessary builds and tests in monorepo CI pipelines.

Community
Advanced
spiriMirrorspiriMirror
307

run-tests

Run Catch2 C++ and pytest Python tests to validate code correctness.

Official
Intermediate
qazuorqazuor

github-actions-patterns

Automates GitHub Actions CI/CD patterns including matrix builds, caching, and reusable workflows.

Community
Basic
shanieMoonlightshanieMoonlight
1

nx-run-tasks

Execute build, test, and lint tasks within an Nx workspace.

Community
Intermediate