Agent skill

Local CI

by module-federation in module-federation/core

Run this repository's local CI parity commands and pnpm run ci:local jobs.

MITAuto-check passedTesting & QA

Install Local CI

skills CLI

$ npx skills add module-federation/core --skill local-ci -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install module-federation/core local-ci --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/local-ci .claude/skills/local-ci && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "local-ci" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/local-ci into .claude/skills/local-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ci", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/module-federation/core/tree/main/.codex/skills/local-ci

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add module-federation/core --skill local-ci -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install module-federation/core local-ci --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/local-ci .agents/skills/local-ci && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "local-ci" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/local-ci into .agents/skills/local-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ci", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add module-federation/core --skill local-ci -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install module-federation/core local-ci --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/local-ci .cursor/skills/local-ci && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "local-ci" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/local-ci into .cursor/skills/local-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ci", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/module-federation/core.git --path .codex/skills/local-ci

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add module-federation/core --skill local-ci -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install module-federation/core local-ci --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/local-ci .gemini/skills/local-ci && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "local-ci" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/local-ci into .gemini/skills/local-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ci", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install module-federation/core local-ci

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add module-federation/core --skill local-ci -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/local-ci .github/skills/local-ci && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "local-ci" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/local-ci into .github/skills/local-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ci", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add module-federation/core --skill local-ci -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install module-federation/core local-ci --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/local-ci .opencode/skills/local-ci && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "local-ci" agent skill from https://github.com/module-federation/core/tree/main/.codex/skills/local-ci into .opencode/skills/local-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-ci", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: local-ci
GitHub stars: 2.7k
Token cost: ~914 tokens
SKILL.md length: 420 words
Files: 3 (incl. references)
Skills in repo: 5
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run this repository's local CI parity commands and pnpm run ci:local jobs.

Works in 4 steps: Inspect available local CI jobs → Pick the smallest matching job → Run commands in CI order → …
Validating a change against the same job shapes used in GitHub Actions
SKILL.md covers Quick Start, Workflow, Common Cases and Notes
Calls pnpm

What it does

Local CI is an agent skill from module-federation/core. Run this repository's local CI parity commands and pnpm run ci:local jobs. Use when validating a change against the same job shapes used in GitHub Actions, choosing the smallest local CI job for a package, workflow, E2E, Metro, devtools, bundle-size, or build-and-test change.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/jobs.md`).

It sits in Testing & QA, covering End-to-end testing, Web performance and CI/CD. It works with GitHub Actions and pnpm. The repository describes itself as: Module Federation is a concept that allows developers to share code and resources across multiple JavaScript applications. The licence is MIT.

When your agent uses it

Validating a change against the same job shapes used in GitHub Actions
Choosing the smallest local CI job for a package
Build-and-test change

Example prompts

“/local-ci”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Inspect available local CI jobs
Pick the smallest matching job
Run commands in CI order
Interpret failures correctly

What it can do on your machine

Read from SKILL.md and the folder at commit d139eed. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Local CI loads about 914 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 420 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~72
When it runs · the whole SKILL.md, loaded when a task matches: ~914
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from module-federation/core at commit d139eed, republished under its MIT licence (© module-federation). 420 words, ~914 tokens.

Download SKILL.mdSave it as .claude/skills/local-ci/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: local-ci
description: Run this repository's local CI parity commands and `pnpm run ci:local` jobs. Use when validating a change against the same job shapes used in GitHub Actions, choosing the smallest local CI job for a package, workflow, E2E, Metro, devtools, bundle-size, or build-and-test change.

Local CI

Use the local CI runner and Turbo/package scripts as the source of truth for validation in this repo.

Quick Start

Start with the smallest deterministic check that matches the change.
Prefer pnpm run ci:local --only=<job> for CI-parity validation.
Prefer direct Turbo or package scripts only when they are the smaller equivalent of the CI job.
Report exactly which command ran, what failed first, and which expected checks were skipped.

Workflow

1. Inspect available local CI jobs

Run:

bash

pnpm run ci:local --list

Use this when the right job is unclear or when the repo may have added or renamed jobs.

For the current job map, read references/jobs.md.

2. Pick the smallest matching job

Use these defaults:

Package code in packages/*: start with build-and-test only if the change is broad; otherwise prefer package build/test commands.
Metro packages or Metro workflow changes: use build-metro, then Metro E2E jobs only if relevant.
E2E app changes: run the matching e2e-* job instead of build-and-test.
Devtools workflow or Playwright/devtools changes: run devtools.
Bundle-size workflow/reporting changes: run bundle-size.
GitHub workflow syntax only: use actionlint locally only to see skip behavior; the actual action is CI-only.
Broad CI, packaging, publint, Turbo, or shared runtime changes: run build-and-test.

3. Run commands in CI order

When reproducing CI, use the same command shape as the repo:

bash

pnpm run ci:local --only=build-and-test
pnpm run ci:local --only=devtools
pnpm run ci:local --only=e2e-runtime

To run more than one job:

bash

pnpm run ci:local --only=build-and-test,bundle-size

Show full SKILL.md (196 more words)Show less

4. Interpret failures correctly

Treat the first failing step as the actionable failure.
Ignore known noisy warnings unless they exit non-zero.
Distinguish repo-wide drift from changed-file gates.
If ci:local fails in Check code format, inspect the changed-file formatter result before running broader builds.
If a dependency build outside the touched scope fails, note it separately as an unrelated blocker.

Common Cases

Broad package or runtime/plugin change

Run:

bash

pnpm run ci:local --only=build-and-test

If that fails on format first, fix the changed files before rerunning the whole job.

One package only

Prefer the smaller direct command first:

bash

pnpm exec turbo run build --filter=@module-federation/<pkg>
pnpm exec turbo run test --filter=@module-federation/<pkg> --force

Then run build-and-test only if the user asks for CI parity or the package change affects shared build/runtime behavior.

E2E change

Run the matching job from references/jobs.md, not the whole matrix.

Workflow change

Use the local CI job if one exists for the workflow's behavior. For workflow syntax, pair local validation with the repo's actionlint path when relevant.

Notes

ci:local sets CI=true and mirrors the repo workflow order.
Some jobs intentionally skip GitHub-only actions such as actionlint and bundle-size-comment.
The repo uses pnpm, Node 24, and Turbo as the standard execution path.
In worktrees, still use Turbo/package scripts directly as documented by the repo instructions.

Files

SKILL.md and 2 other files (references) in .codex/skills/local-ci of module-federation/core.

SKILL.md
agents/openai.yaml
references/jobs.md

Open the folder on GitHubat commit d139eed

Compare with similar skills

Local CI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Local CI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Local CI this skillmodule-federation/core	2.7k	—	~914	Automated safety check: Pass	MIT	today
Deploy Release Testvercel/next.js	143k	—	~1.2k	Automated safety check: Pass	MIT	today
Babysit PRZenUml/web-sequence	150	—	~871	Automated safety check: Pass	MIT	3 days ago
Dokan Run Test Suitegetdokan/dokan	288	—	~4.7k	Automated safety check: Notes	None	yesterday
Actions CI Tuningmizchi/skills	356	—	~2.6k	Automated safety check: Pass	None	6 days ago
Playwright Testmizchi/skills	356	—	~4.7k	Automated safety check: Notes	None	6 days ago

Similar skills

Deploy Release Test
vercel/next.js
Official
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.
143k GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check passed
Babysit PR
ZenUml/web-sequence
Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.
150 GitHub stars~871 tokensUpdated 3 days ago
Testing & QAAuto-check passed
Dokan Run Test Suite
getdokan/dokan
Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions.
288 GitHub stars~4.7k tokensUpdated yesterday
Testing & QAAuto-check: notes
Actions CI Tuning
mizchi/skills
A skill your agent uses when auditing or improving GitHub Actions workflows for a project.
356 GitHub stars~2.6k tokensUpdated 6 days ago
Testing & QAAuto-check passed
Playwright Test
mizchi/skills
Best practices and reference for Playwright Test (E2E). An agent skill from mizchi/skills.
356 GitHub stars~4.7k tokensUpdated 6 days ago
Testing & QAAuto-check: notes
Testing Test Automation Engineer
chendongqi/OPB-Skills
自动化测试助手 - 专业的测试自动化设计与实现专家。适用场景： (1) 自动化测试框架选型与搭建（Selenium/Cypress/Playwright/Appium） (2) 自动化测试脚本编写（Web/API/Mobile） (3) 测试数据管理与Mock设计 (4) CI/CD测试集成（Jenkins/GitLab CI/GitHub Actions） (5) Page…
125 GitHub stars~3.1k tokensUpdated 7 mo ago
Testing & QAAuto-check passed

Questions about Local CI

What does Local CI do?

Run this repository's local CI parity commands and pnpm run ci:local jobs. Local CI is an agent skill from module-federation/core. Run this repository's local CI parity commands and pnpm run ci:local jobs.

When should I use Local CI?

Local CI fits situations like: validating a change against the same job shapes used in GitHub Actions; choosing the smallest local CI job for a package; build-and-test change.

How do I install Local CI in Claude Code?

Run `npx skills add module-federation/core --skill local-ci -a claude-code`. Or copy the skill folder (.codex/skills/local-ci in module-federation/core) into .claude/skills/local-ci in your project. Claude Code loads it when a task matches its description.

How do I install Local CI in Codex?

Run `npx skills add module-federation/core --skill local-ci -a codex`. Or copy the skill folder (.codex/skills/local-ci in module-federation/core) into .agents/skills/local-ci in your project. Codex loads it when a task matches its description.

Can I use Local CI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add module-federation/core --skill local-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/local-ci, .gemini/skills/local-ci, .github/skills/local-ci and .opencode/skills/local-ci in your project.

What does Local CI need to run?

Going by SKILL.md and its folder, Local CI needs the command-line tools its instructions call (pnpm).

Does Local CI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Local CI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Local CI use?

Local CI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Local CI use?

About 914 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 442 tokens, read only when the agent opens those files.

What are the alternatives to Local CI?

Skills that share tags, products or a category with Local CI: Deploy Release Test (vercel/next.js, 143k stars), Babysit PR (ZenUml/web-sequence, 150 stars), Dokan Run Test Suite (getdokan/dokan, 288 stars) and Actions CI Tuning (mizchi/skills, 356 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Local CI?

module-federation (a GitHub organization) maintains it in module-federation/core, which has 2,655 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: module-federation/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Local CI

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Local CI

Quick Start

Workflow

1. Inspect available local CI jobs

2. Pick the smallest matching job

3. Run commands in CI order

4. Interpret failures correctly

Common Cases

Broad package or runtime/plugin change

One package only

E2E change

Workflow change

Notes

Files

Compare with similar skills

Similar skills

More from module-federation/core

Related

Questions about Local CI