B
boranfurkan/typescript-7-migration
Agent skill for migrating to TypeScript 7 (native compiler): official facts, side-by-side 6.0 setup, tooling…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"boranfurkan-typescript-7-migration": {
"command": "npx",
"args": ["skills"]
}
}
}解析自我们于 2026-11-02 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"boranfurkan-typescript-7-migration": {
"command": "npx",
"args": ["skills"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio boranfurkan-typescript-7-migration -- npx skills
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 0 ★ · boranfurkan/typescript-7-migration · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-03 · 最近见到 2026-11-14 · 共见到 12 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 2 个来源 · repo
- 安装
npx skills
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx skills。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: Agent 技能。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
boranfurkan/typescript-7-migration；我们收录于 2026-11-03；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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:
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:
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/boranfurkan-typescript-7-migration/)
- 来源
- github · https://github.com/boranfurkan/typescript-7-migration
- 按领域浏览
- Agent 技能
- 收录来源
- 2 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。