菜单
The workflow for changing webui source code — understand, implement, test, changelog, lint. Use whenever writing or modifying source (not for docs-only edits). Enforces that every behavioral change ships with tests and a changelog entry.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/eclipse-openvsx/openvsx --skill write-code命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Migrate a data-fetching endpoint from the legacy ExtensionRegistryService + fetch-retry pattern to a TanStack Query hook. Only do this when the user explicitly asks — it is an opt-in, in-progress migration. Pairs with the tanstack-query-conventions skill.
How TanStack Query is used in the webui — hook shape, query keys, retries, mutations, options objects, and how consumers read results. Use when writing or reviewing any useQuery/useMutation/useInfiniteQuery code.
How to write unit tests for the webui — the vitest + React Testing Library setup, file layout, harness patterns for context/router-dependent code, and the fail-first check that proves a test actually guards its target. Use when adding or updating tests under test/unit.
基于 SOC 职业分类
| name | write-code |
| description | The workflow for changing webui source code — understand, implement, test, changelog, lint. Use whenever writing or modifying source (not for docs-only edits). Enforces that every behavioral change ships with tests and a changelog entry. |
node_modules for external API types instead of guessing.Every behavioral change ships with tests. This is a gate, not a nicety:
write-tests skill for setup, layout, and harness patterns.yarn test); iterate until green.If a change genuinely has no unit-testable surface (pure styling, config), say so explicitly rather than skipping silently.
Tests are how a change is verified — a passing, fail-first-checked test is the evidence the change works.
Add an entry for the change under ## [next] in CHANGELOG.md, in the right subsection (### Added / ### Changed / ### Fixed / ### Removed / ### Dependencies) — see AGENTS.md for the format rules. This covers product code; test-only, docs, and tooling changes don't get an entry.
yarn lint (full output, no | tail). Fix every error, warning, and info before considering the change done. Never run yarn smoke-tests unless asked. Never commit unless asked.