emp-workflow

Routes EMP repository changes through model selection, validation matrices, and release procedures.

2.4k|230|Updated Oct 29, 2020
One-click install
npx skills add https://github.com/empjs/emp --skill emp-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emp-workflow
Source: https://github.com/empjs/emp/tree/main/skills/emp-workflow
Command: npx skills add https://github.com/empjs/emp --skill emp-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Working in the EMP monorepo involves many boundaries—CI rules, protected paths, release safety, model routing, and worktree hygiene—and this Skill gives an AI agent a single operational guide so changes are scoped, verified, and delivered without violating repository conventions.

Core Features & Use Cases

  • Change Matrix Validation: Maps each change type (docs, package code, CI, release, worktrees) to the minimum required verification commands such as corepack pnpm ci:verify and workflow:check.
  • Model Routing & Delegation: Defines token-first lanes (controller, spark, fast, impl, verifier, deep) and a delegation contract for spawning subagents with bounded briefs.
  • Repository Operations: Covers Git/PR closure, worktree cleanup, Rstest-based test strategy, and release safety rules like dry-run publishing and package scope limits.
  • Use Case: When asked to fix a build issue in packages/cli, the agent reads the routing reference, traces the call path with CodeGraph, edits only the owning package, and runs the matrix-selected checks before reporting changed files and residual risk.

Quick Start

Use the emp-workflow skill to plan and validate my change to the EMP repository with the smallest sufficient verification steps.

Frequently Asked Questions about emp-workflow

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

FAQPage Schema
How do I validate a change in the EMP repository?

Select the smallest checks from the change matrix based on your change type. Documentation edits need `git diff --check` and `corepack pnpm workflow:check`, while package source changes require the relevant acceptance test plus `corepack pnpm ci:verify` and `corepack pnpm empbuild`.

How does the EMP workflow route tasks to different models?

It uses token-first lanes: gpt-5.6-terra low for controller and fast edits, terra medium for bounded multi-file implementation, and read-only gpt-5.6-sol for architecture or release-risk judgment. Escalation happens only when independent verification can catch material risk.

When should I spawn a subagent for EMP repository work?

Spawn a subagent only for an independent domain or medium/high-risk verification, after reading the matching `.codex/agents/` profile. Keep shared-state work, exploratory debugging, and release go/no-go decisions in the controller, and never exceed three direct children.

What files are protected from changes in the EMP repo?

By default you may only touch the task-owning scope: `packages/cdn-*`, `packages/lib-*`, `apps/**`, `website/**`, the publish workflow, and `pnpm-lock.yaml` all require explicit authorization. Generated outputs, caches, `.codegraph/`, and `.worktrees/` must never be committed.

How do I safely clean up Git worktrees in this repository?

Inventory with `git worktree list --porcelain` and `du -sh .worktrees`, then check each candidate's status and diff stat. Remove only clean worktrees with `git worktree remove`, run `git worktree prune`, and never start with `rm -rf .worktrees`.

What are the release safety rules for EMP packages?

CI validates only and must never contain npm credentials or publish commands. Publish scripts require dry-run support and explicit confirmation, automatic release scope stays under `packages/**`, and you must verify package scope, reproducible changelog, `test:rules`, `release:check`, and `ci:verify`.