add-ci-area

Add project directory path filters to GitHub Actions CI workflows.

230|29|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/fpindej/netrock --skill add-ci-area
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: add-ci-area
Source: https://github.com/fpindej/netrock/tree/main/.claude/skills/add-ci-area
Command: npx skills add https://github.com/fpindej/netrock --skill add-ci-area

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating new project directories into your Continuous Integration (CI) pipeline, ensuring that changes in these areas are automatically tested and validated.

Core Features & Use Cases

  • CI Configuration Update: Automates the modification of GitHub Actions workflows (ci.yml and docker.yml) to include new path filters.
  • Job Dependency Management: Ensures new jobs are correctly added to the CI gate, maintaining the integrity of the build process.
  • Use Case: When you create a new microservice within a monorepo, use this Skill to add its directory to the CI's path filters and create corresponding build and test jobs.

Quick Start

Use the add-ci-area skill to add a new 'mobile' project area to the CI configuration.

Frequently Asked Questions about add-ci-area

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

FAQPage Schema
How do I add a new project directory to GitHub Actions CI workflows?โ–ผ

Adding a new microservice to CI path filters triggers automated testing for that directory. This Skill updates ci.yml and docker.yml job dependencies and path filters, ensuring new service modules or frontend apps integrate smoothly into existing CI pipelines.

What is a path filter in continuous integration?โ–ผ

A path filter in continuous integration restricts workflow execution to specific directory changes. This Skill configures these filters in GitHub Actions workflows so automated build and test jobs only trigger when new project areas are modified.

How do I configure CI job dependencies for a new monorepo service?โ–ผ

Configuring CI job dependencies for a new monorepo service involves adding the new directory path to workflow files and updating the CI gate. This ensures the new build and test jobs are correctly executed before merging.

Does adding a new area to GitHub Actions workflows require manual verification?โ–ผ

Yes, adding a new area to GitHub Actions workflows requires manual verification. After updating the ci.yml and docker.yml job dependencies and path filters, you must manually verify that the build, lint, and test steps execute successfully for the new area.

Why are my GitHub Actions not triggering for a new project path?โ–ผ

GitHub Actions may not trigger for a new project path if the directory is missing from the workflow path filters. You need to update the ci.yml and docker.yml files to include the new service module directory in the CI configuration.