Migrate to Deno
denoland/skills
Moves a Node.js, npm, Yarn, pnpm or Bun project to Deno in reversible steps, starting with Deno as the package manager and changing no code unless needed.
What a dependency migration must do before it is finished, regardless of how good the code is.
Install Migration Completeness
$ npx skills add diyanbogdanov/emend --skill migration-completeness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install diyanbogdanov/emend migration-completeness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/diyanbogdanov/emend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/migration-completeness .claude/skills/migration-completeness && rm -rf skills-srcUse ~/.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/
Install the "migration-completeness" agent skill from https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completeness into .claude/skills/migration-completeness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-completeness", 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 install https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completenessType 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.
$ npx skills add diyanbogdanov/emend --skill migration-completeness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install diyanbogdanov/emend migration-completeness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diyanbogdanov/emend.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/migration-completeness .agents/skills/migration-completeness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migration-completeness" agent skill from https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completeness into .agents/skills/migration-completeness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-completeness", 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.
$ npx skills add diyanbogdanov/emend --skill migration-completeness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install diyanbogdanov/emend migration-completeness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diyanbogdanov/emend.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/migration-completeness .cursor/skills/migration-completeness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "migration-completeness" agent skill from https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completeness into .cursor/skills/migration-completeness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-completeness", 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 https://github.com/diyanbogdanov/emend.git --path skills/migration-completeness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add diyanbogdanov/emend --skill migration-completeness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install diyanbogdanov/emend migration-completeness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diyanbogdanov/emend.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/migration-completeness .gemini/skills/migration-completeness && rm -rf skills-srcUse ~/.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/
Install the "migration-completeness" agent skill from https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completeness into .gemini/skills/migration-completeness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-completeness", 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.
$ gh skill install diyanbogdanov/emend migration-completenessInstalls 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).
$ npx skills add diyanbogdanov/emend --skill migration-completeness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/diyanbogdanov/emend.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/migration-completeness .github/skills/migration-completeness && rm -rf skills-srcUse ~/.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/
Install the "migration-completeness" agent skill from https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completeness into .github/skills/migration-completeness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-completeness", 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.
$ npx skills add diyanbogdanov/emend --skill migration-completeness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install diyanbogdanov/emend migration-completeness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/diyanbogdanov/emend.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/migration-completeness .opencode/skills/migration-completeness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "migration-completeness" agent skill from https://github.com/diyanbogdanov/emend/tree/main/skills/migration-completeness into .opencode/skills/migration-completeness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-completeness", 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
migration-completeness- GitHub stars
- 58
- Token cost
- ~542 tokens
- SKILL.md length
- 330 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
What a dependency migration must do before it is finished, regardless of how good the code is.
- Works in 5 steps: Finish the migration first. If you are… → Correct every comment the migration… → Behaviour must not change. The one… → …
- Tasks that involve Code migrations
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Dependency management
What it does
Migration Completeness is an agent skill from diyanbogdanov/emend. What a dependency migration must do before it is finished, regardless of how good the code is. Always applied; the quality skill composes on top.
Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code migrations and Dependency management. It works with npm, OpenAPI and TypeScript. The repository describes itself as: Verified AI dependency migrations. Finds which of your lines a version bump actually breaks, fixes them, and proves the result still compiles and passes your tests. The licence is MIT.
When your agent uses it
- Tasks that involve Code migrations
- Tasks that involve Dependency management
Example prompts
- “/migration-completeness”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Finish the migration first. If you are told a deprecated symbol is still
- Correct every comment the migration falsified. A comment naming the old
- Behaviour must not change. The one exception is rule 1: replacing a
- **When a coercion has to stand in for missing data, prefer a value the caller
- If the migration is already complete and good, change nothing and say why.
What it can do on your machine
Read from SKILL.md and the folder at commit f8b72b0. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Migration Completeness loads about 542 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 330 words of instructions outside code blocks.
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 diyanbogdanov/emend at commit f8b72b0, republished under its MIT licence (© diyanbogdanov). 330 words, ~542 tokens.
Download SKILL.mdSave it as
.claude/skills/migration-completeness/SKILL.md (or your agent's skills folder).- name
- migration-completeness
- description
- What a dependency migration must do before it is finished, regardless of how good the code is. Always applied; the quality skill composes on top.
Migration Completeness
You are reviewing a dependency migration that already compiles and passes its tests. Passing is the floor, not the goal.
This skill is about whether the migration is finished. A separate quality skill judges whether the result is good. Both apply, and this one outranks it: a beautifully restructured migration that still uses the deprecated API has not done what it said.
Rules
Finish the migration first. If you are told a deprecated symbol is still in use, replacing it is the highest-priority edit in this pass. A migration that reports "X is deprecated", titles its commit after X, and ships with X still in the code has not done what it said. Use the package's supported replacement; if there is genuinely none, leave it and say so.
Correct every comment the migration falsified. A comment naming the old version, or describing behaviour the change altered, is now wrong, and a migration that leaves a false comment behind has not finished. Rewrite it to describe what the code does now, in a form that reads correctly on its own — do not repeat a sentence that already appears beside it, and do not leave a fragment of the old one.
A comment the migration did not falsify stays exactly as it is.
Behaviour must not change. The one exception is rule 1: replacing a deprecated API with its supported equivalent is the migration finishing its job, not a behaviour change.
When a coercion has to stand in for missing data, prefer a value the caller can detect over one it cannot.
Number(x ?? 0)renders a real string as "0", which no test objects to and no reader spots; returning null, or a sentinel the formatter understands, keeps the absence visible.If the migration is already complete and good, change nothing and say why. That is a valid and useful answer. A pass that invents work to look busy is worse than one that declines.
© diyanbogdanov, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/migration-completeness of diyanbogdanov/emend.
Open the folder on GitHubat commit f8b72b0
Compare with similar skills
Migration Completeness 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Migration Completeness this skilldiyanbogdanov/emend | 58 | — | ~542 | Automated safety check: Pass | MIT | |
| Migrate to Denodenoland/skills | 100 | — | ~2.2k | Automated safety check: Warn | MIT | |
| Linea Dependency MaintenanceConsensys-Incorporated/linea-attestation-registry | 177 | 1 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Dependabot Alerts Updatelivesession/xyd | 114 | — | ~2k | Automated safety check: Pass | MIT | |
| Deno Runtime and Package Managerdenoland/skills | 100 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Monorepo Tooling and Dependenciespierrecomputer/pierre | 6.3k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Linea Dependency Maintenance
Consensys-Incorporated/linea-attestation-registry
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…
Dependabot Alerts Update
livesession/xyd
Automatically fetch and fix Dependabot security alerts by querying GitHub REST API for open alerts, identifying vulnerable packages, researching secure versions, and updating package.json files…
- Official
Deno Runtime and Package Manager
denoland/skills
Guides writing, running and configuring Deno 2.9+ projects: installing npm and JSR dependencies, permissions, config file precedence and the built-in fmt, lint, test and compile toolchain.
Monorepo Tooling and Dependencies
pierrecomputer/pierre
Sets one monorepo's rules for toolchain pins, pnpm package operations, the shared dependency catalog and moon tasks, so the agent adds versions and scripts the right way.
Fix Security PR
unional/typescript-blackbook
Fix a PR that is failing due to security or vulnerability issues — npm/pnpm/yarn/bun audit failures, CVE alerts, Dependabot merge conflicts, Snyk failures, or GitHub security advisory blocks.
More from diyanbogdanov/emend
Thermo Nuclear Code Quality Review
diyanbogdanov/emend
An extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth.
Related
Works with
Categories
Questions about Migration Completeness
What does Migration Completeness do?
What a dependency migration must do before it is finished, regardless of how good the code is. Migration Completeness is an agent skill from diyanbogdanov/emend. What a dependency migration must do before it is finished, regardless of how good the code is.
When should I use Migration Completeness?
Migration Completeness fits situations like: tasks that involve Code migrations; tasks that involve Dependency management.
How do I install Migration Completeness in Claude Code?
Run `npx skills add diyanbogdanov/emend --skill migration-completeness -a claude-code`. Or copy the skill folder (skills/migration-completeness in diyanbogdanov/emend) into .claude/skills/migration-completeness in your project. Claude Code loads it when a task matches its description.
How do I install Migration Completeness in Codex?
Run `npx skills add diyanbogdanov/emend --skill migration-completeness -a codex`. Or copy the skill folder (skills/migration-completeness in diyanbogdanov/emend) into .agents/skills/migration-completeness in your project. Codex loads it when a task matches its description.
Can I use Migration Completeness 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 diyanbogdanov/emend --skill migration-completeness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migration-completeness, .gemini/skills/migration-completeness, .github/skills/migration-completeness and .opencode/skills/migration-completeness in your project.
What does Migration Completeness need to run?
SKILL.md names no scripts, command-line tools or credentials: Migration Completeness is instructions for the agent only.
Does Migration Completeness 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 Migration Completeness 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 Migration Completeness use?
Migration Completeness 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 Migration Completeness use?
About 542 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Migration Completeness?
Skills that share tags, products or a category with Migration Completeness: Migrate to Deno (denoland/skills, 100 stars), Linea Dependency Maintenance (Consensys-Incorporated/linea-attestation-registry, 177 stars), Dependabot Alerts Update (livesession/xyd, 114 stars) and Deno Runtime and Package Manager (denoland/skills, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migration Completeness?
diyanbogdanov (a GitHub user) maintains it in diyanbogdanov/emend, which has 58 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.
Source: diyanbogdanov/emend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.