moonrepo
Manage monorepos and task orchestration with moonrepo — a Rust-based build system for JavaScript/TypeScript projects. Use when someone asks to "manage a monorepo", "moonrepo", "task runner for monorepo", "faster than Turborepo", "build system with dependency graph", or "monorepo tooling". Covers project configuration, task orchestration, dependency graph, caching, CI optimization, and toolchain management.
What this skill does
# moonrepo
## Overview
moonrepo (moon) is a Rust-based monorepo management tool and task runner. It understands your project dependency graph, runs tasks in the correct order with caching, manages toolchain versions (Node.js, Bun, etc.), and generates CI pipelines automatically. Faster and more deterministic than Turborepo, with built-in toolchain management that Nx doesn't have.
## When to Use
- Managing a monorepo with multiple packages/apps
- Need deterministic task execution with dependency-aware ordering
- Want consistent toolchain versions across the team
- CI is slow because it builds everything on every PR
- Need better caching than npm scripts provide
## Instructions
### Setup
```bash
# Install moon CLI
npm install -D @moonrepo/cli
# Initialize in your monorepo
moon init
```
### Workspace Configuration
```yaml
# .moon/workspace.yml — Monorepo root config
projects:
- "apps/*"
- "packages/*"
vcs:
manager: git
defaultBranch: main
runner:
cacheLifetime: 7d
logStyle: stream
```
### Toolchain Management
```yaml
# .moon/toolchain.yml — Pin Node.js and package manager versions
node:
version: "20.11.0"
packageManager: pnpm
pnpm:
version: "9.1.0"
# Automatically downloads and uses these exact versions
# No more "works on my machine" — everyone uses the same toolchain
```
### Project Configuration
```yaml
# apps/web/moon.yml — Project-level config
type: application
language: typescript
dependsOn:
- "packages/ui"
- "packages/shared"
tasks:
dev:
command: next dev
local: true # Only runs locally, not in CI
build:
command: next build
inputs:
- "src/**/*"
- "package.json"
- "next.config.js"
outputs:
- ".next"
deps:
- "packages/ui:build" # Build ui package first
- "packages/shared:build"
test:
command: vitest run
inputs:
- "src/**/*"
- "tests/**/*"
lint:
command: oxlint src/
inputs:
- "src/**/*"
```
```yaml
# packages/ui/moon.yml — Shared UI library
type: library
language: typescript
tasks:
build:
command: tsup
inputs:
- "src/**/*"
- "tsup.config.ts"
outputs:
- "dist"
test:
command: vitest run
inputs:
- "src/**/*"
- "tests/**/*"
```
### Run Tasks
```bash
# Run a task in a specific project
moon run web:build
# Run task across all projects that have it
moon run :test
# Run with dependency graph (builds deps first)
moon run web:build # Automatically builds packages/ui first
# Check what would run (dry run)
moon run web:build --dryRun
# Run affected tasks only (based on git diff)
moon run :test --affected
```
### CI Optimization
```yaml
# .github/workflows/ci.yml — Only run what changed
name: CI
on: [pull_request]
jobs:
ci:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # Full history for affected detection
- uses: moonrepo/setup-toolchain@v0
- run: moon ci # Runs all affected tasks in optimal order
```
```bash
# moon ci does:
# 1. Detects which files changed in the PR
# 2. Determines which projects are affected
# 3. Runs only the affected tasks in dependency order
# 4. Uses cache for unchanged outputs
```
## Examples
### Example 1: Set up a new monorepo
**User prompt:** "I have a Next.js app and 3 shared packages. Set up a monorepo with proper task orchestration."
The agent will initialize moon, configure workspace projects, define tasks with proper inputs/outputs/deps, and set up CI with affected detection.
### Example 2: Migrate from Turborepo
**User prompt:** "Our Turborepo setup is getting complex. Migrate to moonrepo."
The agent will translate turbo.json pipeline to moon task configs, set up toolchain management, and configure CI with moon's affected detection.
## Guidelines
- **`inputs` and `outputs` for caching** — define what files affect a task and what it produces
- **`deps` for task ordering** — `"packages/ui:build"` runs before `"web:build"`
- **`--affected` for CI** — only run tasks for changed projects
- **`moon ci` is the CI command** — handles affected detection, ordering, and caching
- **Toolchain pinning** — everyone uses exactly the same Node.js/pnpm version
- **`type: application` vs `library`** — affects dependency graph behavior
- **`local: true` for dev tasks** — skipped in CI automatically
- **Project references via `dependsOn`** — moon understands the monorepo graph
- **Cache is content-addressed** — same inputs = cache hit, regardless of branch
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.