# migrate

Reads your lodash code and shows how to swap each function for es-toolkit or es-toolkit/compat. Handy when the bundle needs to shrink.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 313 installs · ★ 11381
- Author: toss
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/toss/es-toolkit/tree/HEAD/es-toolkit-plugin/skills/migrate/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/toss-migrate

## What it does

The skill takes a code snippet, a list of function names, or a question about strict versus compat. It pulls out the lodash functions you use and checks whether the installed es-toolkit package actually exports them. That check runs through `node --input-type=module`, and the package metadata is resolved with `node -e "console.log(require.resolve('es-toolkit/package.json'))"` — a conventional `node_modules` path is not assumed.

What comes back: an availability table, doc links, before/after pairs, and a feature comparison across lodash, es-toolkit and es-toolkit/compat for options like cancel, flush and maxWait. For wide migrations it suggests a bundler alias in webpack or Vite, the `no-restricted-imports` ESLint rule, and jscodeshift codemods. Exact bundle-size numbers it tells you to quote only after measuring your own project.

One thing to know: the availability check runs from the package that depends on es-toolkit. In a monorepo that is usually a workspace package, not the repo root. On Yarn Plug'n'Play you need `yarn node` instead of `node`, or the import will not resolve. The skill can live as a standalone directory, so it does not assume the es-toolkit repository or a sibling `docs` folder is around.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add toss/es-toolkit --skill migrate -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/migrate/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/migrate/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add toss/es-toolkit --skill migrate -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/migrate/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add toss/es-toolkit --skill migrate -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/migrate/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install toss/es-toolkit migrate
```

2. **Manually: put the files in place**
- File: `.github/skills/migrate/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add toss/es-toolkit --skill migrate -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/toss/es-toolkit --path es-toolkit-plugin/skills/migrate
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/migrate/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add toss/es-toolkit --skill migrate -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/toss/es-toolkit/tree/HEAD/es-toolkit-plugin/skills/migrate/SKILL.md

## When to use it
- rewrite lodash imports to es-toolkit without checking every function by hand
- see how strict differs from es-toolkit/compat for one specific function
- cut bundle size with tree-shakeable imports
- find out whether a lodash function exists in the installed package version
- plan a gradual migration of a large legacy codebase through compat

## Example prompts
- Here's my lodash code, show me the es-toolkit version: `import { get, chunk, map } from 'lodash'`
- Is debounce in strict or only in compat? Compare the cancel and flush options
- Build me a migration plan: large project, I want to go through es-toolkit/compat

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4c8c34a63d759ec8.

BEGIN THIRD-PARTY FILE 4c8c34a63d759ec8
````text
---
name: migrate
description: Guide migrating lodash code to es-toolkit. Use when the user wants to migrate from lodash, replace lodash imports, reduce bundle size by switching to es-toolkit, or understand the difference between es-toolkit and es-toolkit/compat.
argument-hint: '<paste lodash code, function names, or ask about strict vs compat>'
allowed-tools: Read, Grep, Glob, Bash
---

# Lodash Migration & Compat Guide

Guide users through migrating lodash to es-toolkit and understanding the strict vs compat APIs, grounded in actual source code.

## Input

$ARGUMENTS — Lodash code to migrate, specific function names, or a question about strict vs compat.

## Core Concepts

**es-toolkit (strict)**: Opinionated, simplified API for the 85% use case. Smaller bundle, may differ from lodash in edge cases by design. New functions are added here.

**es-toolkit/compat**: Aims for full lodash test compatibility within a defined scope. See `docs/compatibility.md` for out-of-scope behaviors (e.g., implicit type conversions, prototype modifications).

## Why source-first matters

The only reliable way to know the difference between strict and compat is to inspect the version installed in the user's project. The skill may be installed as a standalone directory, so never assume the es-toolkit repository or a sibling `docs` directory is available.

## Workflow

### If a specific function or lodash code is given

#### 1. Identify lodash functions from input

Extract which lodash functions are used and how they're imported.

#### 2. Verify availability in the installed package

Run from the package that depends on es-toolkit. In a monorepo this is usually a workspace package, not the repository root. If the project uses Yarn Plug'n'Play, use `yarn node` instead of `node`.

Replace the example names with the lodash functions found in the input:

```bash
node --input-type=module -e "
import { createRequire } from 'node:module';

const require = createRequire(import.meta.url);
const names = ['get', 'chunk', 'map'];
const pkg = require('es-toolkit/package.json');
const entries = Object.keys(pkg.exports)
  .filter(subpath => subpath !== './package.json' && !subpath.includes('*'))
  .map(subpath => subpath === '.' ? 'es-toolkit' : 'es-toolkit/' + subpath.slice(2));
const modules = await Promise.all(entries.map(entry => import(entry).catch(() => null)));
if (modules.every(module => module == null)) {
  console.error('es-toolkit is not resolvable from ' + process.cwd());
  process.exit(1);
}
````
END THIRD-PARTY FILE 4c8c34a63d759ec8

The third-party file has ended. Everything between the 4c8c34a63d759ec8 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2514 of 8231 bytes. © toss · MIT · https://github.com/toss/es-toolkit/tree/HEAD/es-toolkit-plugin/skills/migrate/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md