菜单
Research why the TypeScript team made a specific typing decision. Use when evaluating whether ts-reset should override a built-in type, or when triaging issues that propose type changes. Searches the microsoft/TypeScript repo for relevant issues, PRs, and team comments.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mattpocock/ts-reset --skill research-ts-decisions命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | research-ts-decisions |
| description | Research why the TypeScript team made a specific typing decision. Use when evaluating whether ts-reset should override a built-in type, or when triaging issues that propose type changes. Searches the microsoft/TypeScript repo for relevant issues, PRs, and team comments. |
| user-invocable | true |
When evaluating whether ts-reset should override a TypeScript built-in type, research what the TypeScript team has said about it. Understanding their reasoning lets us make informed decisions — either agreeing with their trade-off or deliberately choosing a different one.
Ryan Cavanaugh (@RyanCavanaugh) is the TypeScript project lead and usually the one making final verdicts on typing decisions. His comments carry the most weight. Also look for comments from:
@DanielRosenwasser) — TS program manager@AHejlsberg) — original designer@sandersn)Use gh to search the microsoft/TypeScript repo. Try multiple queries — the issue might be about the specific method, the return type, or a broader pattern:
# Search issues by title/body
gh search issues --repo microsoft/TypeScript "Object.create return type" --limit 20
gh search issues --repo microsoft/TypeScript -- 20
Once you have candidate issues, fetch comments and filter for TypeScript team members:
# Get Ryan's comments on a specific issue
gh api repos/microsoft/TypeScript/issues/{number}/comments \
--jq '.[] | select(.user.login == "RyanCavanaugh") | {html_url, body}'
# Check for team comments more broadly
gh api repos/microsoft/TypeScript/issues/{number}/comments \
--jq '.[] | select(.user.login == "RyanCavanaugh" or .user.login == "DanielRosenwasser" or .user.login == "sandersn" or .user.login == "ahejlsberg") | {user: .user.login, html_url, body}'
Many typing decisions were tried, broke things, and got reverted. This history is critical:
# Search for PRs related to the topic
gh search prs --repo microsoft/TypeScript "Object.create" --limit 20
# Check if a PR was later reverted
gh api repos/microsoft/TypeScript/pulls/{number} --jq '{title, state, merged_at, body}'
TypeScript team members often state general principles on tangentially related issues. If the specific method doesn't have much discussion, search for related patterns:
# Example: if researching Object.create, also check Object.getPrototypeOf,
# or broader topics like "prototype typing" or "returns any"
gh search issues --repo microsoft/TypeScript "Object.getPrototypeOf any" --limit 10
If GitHub search doesn't surface enough, use web search:
site:github.com/microsoft/TypeScript "Object.create" RyanCavanaugh
Structure your findings as:
Always include direct permalink URLs to specific comments, not just issue URLs. Use the html_url field from the GitHub API.
These recurring arguments come up frequently. Knowing them helps you search more effectively and contextualize what you find:
any can never be wrong, just less right" — Ryan's principle that any is a safe default that never produces false errorsPropertyDescriptorMap is untyped — any API that takes property descriptors can't carry type information through them