菜单
Update the agent knowledge base after making code changes in the Roslyn repo. Run at the end of every task that modifies code, adds files, changes public APIs or diagnostics, or establishes new patterns. Keeps .github/memory/ fresh and reliable.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dotnet/roslyn --skill update-agent-docs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Set up tracking for a new C# compiler feature: create test plan issue, feature label, update Language Feature Status page, and link related PRs. Use when: setting up a new language feature, creating a test plan, tracking a new csharplang proposal in roslyn, or asked to 'set up feature tracking'.
Create a merge branch from a chosen base, merge a chosen source/upstream branch into it, resolve common Roslyn conflicts (`.xlf`, `.resx`, compiler codegen), and summarize the resolutions.
Review code changes in dotnet/roslyn for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.
正在显示 SKILL.md
基于 SOC 职业分类
| name | update-agent-docs |
| description | Update the agent knowledge base after making code changes in the Roslyn repo. Run at the end of every task that modifies code, adds files, changes public APIs or diagnostics, or establishes new patterns. Keeps .github/memory/ fresh and reliable. |
Run at the end of every task that changes code. This is not optional.
Files added or moved? → Update .github/memory/FILE_MAP.md (top-level area) and the matching .github/instructions/<area>.instructions.md (directory detail).
Memory file added, removed, renamed, or had its purpose change? → Update .github/memory/INDEX.md and any memory files that reference it.
Public API changed? → Update the matching .github/instructions/<area>.instructions.md (Compiler/IDE) and the owning project's PublicAPI.Unshipped.txt (RS0016 enforces this). API_MAP.md covers only repo-wide entry points.
New compiler error code, IDE diagnostic ID, or resource string added? → Reflect it in the matching .github/instructions/<area>.instructions.md; ensure ErrorCode.cs / IDEDiagnosticIds.cs / .resx (+ /t:UpdateXlf) are consistent.
New pattern established? → If repo-wide, add to .github/memory/CONVENTIONS.md; if layer-specific, add to the matching .github/instructions/<area>.instructions.md.
Surprising or undocumented behavior found? → Repo-wide → .github/memory/KNOWN_ISSUES.md; layer-specific → .github/memory/known-issues/<area>.md.
Changed test base classes, locations, or how to run a suite? → Repo-wide layout → .github/memory/TESTING_STRATEGY.md; layer-specific bases/conventions → .github/memory/testing/<area>.md.
Any doc updated? → No additional tracking needed. Git history tracks changes automatically.
Documentation must describe the repository's current state, not the history or mechanics of the change being made. Do not add guidance that only makes sense in the context of the current diff, mentions behavior removed by the task, or warns against a workaround that no longer exists. Before adding guidance, ask whether it would help a future contributor starting from a clean checkout; if not, leave it out.
If knowledge doesn't fit existing files:
.github/memory/ with a descriptive name (e.g., incremental-generators.md, not misc.md).coverage field describing what it covers..github/memory/INDEX.md.You do not need permission to create new files in .github/memory/. This space is yours to evolve.
New docs should have minimal frontmatter — only the coverage field:
---
coverage: Brief description of what this doc covers
---
Do NOT add last_updated, updated_by, confidence, or date fields. Git history provides this without creating merge conflicts.