Run any Skill in Manus with one click

update-agent-docs

Stars20,526

Forks4,283

UpdatedJuly 1, 2026 at 20:32

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dotnet

dotnet/roslyn

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

Update Agent Docs

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

Checklist

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.

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.

More from this repository

same repository

validate-sdk

dotnet/roslyn

Install and validate a .NET SDK from an Azure DevOps internal build. Use this when asked to install, validate, or set up a .NET SDK from a dnceng/internal Azure DevOps build link or build ID.

2026-07-0620.5k

code-review

dotnet/roslyn

Review code changes in dotnet/roslyn for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.

2026-07-0220.5k

analyzer-codefix

dotnet/roslyn

Create or modify Roslyn IDE analyzers, code fixes, and code refactorings. Use when: adding a new IDE diagnostic (IDE0xxx), implementing a CodeFixProvider, implementing a CodeRefactoringProvider, writing analyzer/fixer tests, or working with AbstractBuiltInCodeStyleDiagnosticAnalyzer. Also use for: diagnostic analyzer, code action, FixAllProvider, TestInRegularAndScriptAsync, TestMissingInRegularAndScriptAsync.

2026-06-2220.5k

snap

dotnet/roslyn

Perform a branch snap (release branch cut) for dotnet repos like dotnet/roslyn. Use when: snapping a branch, cutting a release branch, creating a release branch, merging main into release, updating VS insertion config, updating darc subscriptions for a snap, moving milestones, or asked about snap workflow.

2026-05-0520.5k

formatting-log

dotnet/roslyn

Import Razor formatting log zips that the user has already downloaded from Azure DevOps feedback tickets or GitHub issues into FormattingLogTest, validate whether the captured problem still reproduces, and if needed drive a minimal repro plus fix workflow.

2026-04-3020.5k

new-compiler-feature

dotnet/roslyn

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'.

2026-04-2820.5k

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.

Update Agent Docs

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

Checklist

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.

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.

Any doc updated? → No additional tracking needed. Git history tracks changes automatically.

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.