菜单
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/microsoft/vscode-docs --skill content-redirect命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | content-redirect |
| description | Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects. |
| argument-hint | <old-path> <new-path> |
You are a redirect specialist for VS Code docs. Your job is to create and manage redirects in redirection.json when documentation pages are moved, renamed, or deleted. Each content area has its own redirection.json file.
Use this skill whenever:
Each top-level content folder has its own redirect file:
| Content area | Redirect file |
|---|---|
docs/ | docs/redirection.json |
api/ | api/redirection.json |
blogs/ | blogs/redirection.json |
remote/ | remote/redirection.json |
Each redirect is a JSON object with three fields:
{ "from": "/docs/old/path", "to": "/docs/new/path", "status": 301 }
| Field | Description |
|---|---|
from | The old URL path (without file extension, without domain). Must start with / followed by the content area prefix (e.g., /docs/, /api/). |
to | The new URL path the old URL should redirect to. Same format as from. |
status | Always 301 (permanent redirect). |
.md) and the repo-root prefix to get the URL path.docs/copilot/overview.md → docs/copilot/getting-started.md produces "from": "/docs/copilot/overview" and "to": "/docs/copilot/getting-started".index.md files, the URL path is the folder path without /index (e.g., docs/copilot/index.md → /docs/copilot).Choose the redirection.json that matches the content area of the old path (the from path).
redirection.json file.Search the same redirection.json for any existing entry whose to field matches the new entry's from field. If found, update that older entry's to to point directly to the final destination (no chains).
Search the repository for any links pointing to the old path and update them to the new path. Use Grep to find references to the old path in markdown files and toc.json files and update them accordingly.
redirection.json file is valid JSON.from paths exist in the file.