How do I install the Update Agent Docs skill?

Run npx skillmds@latest add dotnet/update-agent-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Agent Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Agent Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Agent Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Agent Docs?

.NET (Microsoft) (@dotnet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Agent Docs by dotnet — Agent Skill

Name: Update Agent Docs
Rating: 4.2 (5 reviews)
Author: .NET (Microsoft)

Update Agent Docs

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.

.NET (Microsoft) Updated Sep 9, 2026 4k repo stars

File contents

Update Agent Docs

Run at the end of every task that changes code. This is not optional.

Checklist

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 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? → 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? → Ask the user how they want it documented.

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 Quality

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.

Creating New Doc Files

If knowledge doesn't fit existing files:

Create a new file in .github/memory/ with a descriptive name (e.g., incremental-generators.md, not misc.md).
Add YAML frontmatter with a coverage field describing what it covers.
Add a row to .github/memory/INDEX.md.

You do not need permission to create new files in .github/memory/. This space is yours to evolve.

Frontmatter Format

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.

---name: update-agent-docsdescription: 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.--- # Update Agent Docs Run at the end of every task that changes code. This is not optional. ## Checklist **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 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?** → 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?** → Ask the user how they want it documented. **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 Quality 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. ## Creating New Doc Files If knowledge doesn't fit existing files: - Create a new file in `.github/memory/` with a descriptive name (e.g., `incremental-generators.md`, not `misc.md`). - Add YAML frontmatter with a `coverage` field describing what it covers. - Add a row to `.github/memory/INDEX.md`. You do not need permission to create new files in `.github/memory/`. This space is yours to evolve. ## Frontmatter Format New docs should have minimal frontmatter — only the `coverage` field: ```yaml --- 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.

Frequently asked questions

Update Agent Docs

File contents

Update Agent Docs

Checklist

Documentation Quality

Creating New Doc Files

Frontmatter Format

Related skills

Frequently asked questions

How do I install the Update Agent Docs skill?

What does the Update Agent Docs skill do?

Is Update Agent Docs safe to use?

Which AI agents work with Update Agent Docs?

Is Update Agent Docs free to use?

Who published Update Agent Docs?