Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
B

boranfurkan/typescript-7-migration

Agent skill for migrating to TypeScript 7 (native compiler): official facts, side-by-side 6.0 setup, tooling…

Before you install: no copy-paste command · license MIT · link reachable

First step: npx skills add boranfurkan/typescript-7-migration

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
  "mcpServers": {
    "boranfurkan-typescript-7-migration": {
      "command": "npx",
      "args": ["skills"]
    }
  }
}

Parsed from the README we fetched on 2026-11-02; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
  "servers": {
    "boranfurkan-typescript-7-migration": {
      "command": "npx",
      "args": ["skills"]
    }
  }
}
Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio boranfurkan-typescript-7-migration -- npx skills
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
Star count
0 ★ · boranfurkan/typescript-7-migration · read from the GitHub search API · (checked 2026-11-13 20:00:50)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-03 · last seen 2026-11-14 · seen 12× · listed by 2 sources
Score
score 203 · 2 sources · repo
Install
npx skills
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx skills. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository boranfurkan/typescript-7-migration;first catalogued 2026-11-03;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# TypeScript 7 Migration Skill

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Lets your coding agent upgrade projects to TypeScript 7 correctly, using facts from the official release notes
instead of guesses.
Works with Claude Code, Codex, Cursor, Gemini CLI and any agent that reads Agent Skills (SKILL.md).
TypeScript 7.0 (July 2026) is the Go-native compiler: about 10× faster type-checking. It shipped after the training
cutoff of today's models. They know the general direction (6.0 deprecations, "native port") but hedge or guess on
the details that decide whether your upgrade works:
7.0 has no compiler API. typescript-eslint, vue-tsc/Volar, ts-node, ts-jest, ts-patch transformers and any
script using ts.createProgram must stay on 6.0, via the official @typescript/typescript6 package.
Hard errors: target: es5, downlevelIteration, moduleResolution: node, baseUrl,
esModuleInterop: false, outFile, AMD/UMD/System modules, and more.
Silent default changes: types is now [] ("Cannot find name 'describe'") and rootDir is the tsconfig's
directory (output moves to dist/src/).
How to run 6.0 and 7.0 side by side with npm aliases.
### Eval results
Graders passed (LLM judge = Sonnet, 3 votes per grader), 2 runs per arm, one table cell per run.
| Case | Sonnet without | Sonnet with | Haiku without | Haiku with |
| ts7-tooling-migration-plan (3 graders) | 0/3, 0/3 | 3/3, 3/3 | 0/3, 0/3 | 2/3, 2/3 |
| upgrade-node-service-to-ts7 (4 graders) | 3/4, 4/4 | 4/4, 4/4 | 2/4, 2/4 | 3/4, 4/4 |
| ts7-post-upgrade-breakage (2 graders) | 1/2, 2/2 | 2/2, 1/2 | 2/2, 1/2 | 2/2, 2/2 |
| Total | 10/18 | 17/18 | 7/18 | 15/18 |
## Read this before trusting the numbers
Small samples: 2 runs per arm per case. Differences of a point or two are noise.
Offline agents: the agents had no web tools. Real agents with web access may find these facts themselves, so real-world gains are likely smaller.
Same author: the skill and the graders were written by the same person from the same release notes.
One mechanism-specific grader: it requires the @typescript/typescript6 side-by-side mechanism specifically.
Strict graders: the two with-skill misses are judged strictness, not wrong answers. Haiku tooling grader 1 bundles "no API in 7.0", "new API in 7.1" and "ts-patch can't run" into one check; both answers got the substance right but omitted the 7.1 mention. Sonnet post-upgrade run 2 explained the types default and fixed it, but split node/jest across two tsconfigs, and the judge voted 1-2.
Skill edited mid-evaluation: after the first Haiku with-skill runs I added a line to SKILL.md telling the agent to state the "7.0 has no compiler API" reason explicitly, then re-ran Haiku on the tooling and upgrade cases. Scores did not improve (tooling 2/3, 2/3 again; upgrade 4/4, 3/4), so the table keeps the original runs. The Sonnet runs used the earlier SKILL.md wording.
Facts date: as of TypeScript 7.0, re-checked 2026-11-02 (7.1 was still in beta).
The same author also made a benchmark of a data-analysis skill where gains were much smaller.
## Install
Claude Code (plugin):
/plugin marketplace add boranfurkan/typescript-7-migration
/plugin install typescript-7-migration@typescript-7-migration
Any agent supporting Agent Skills:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/boranfurkan-typescript-7-migration/)
Source
github · https://github.com/boranfurkan/typescript-7-migration
Browse by field
Agent skills
Listed by
2 independent sources
added
today

More like this

All 420 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index