vssdktestfx
AGENTS.md23 starsChanged 4 months agoMITView on GitHub
* Review the CONTRIBUTING.md file for instructions to build and test the software. * Run the .github/Prime-ForCopilot.ps1 script (once) before running any dotnet or msbuild commands. If you see any build errors about not finding git objects or a shallow clone, it may be time to run this script again.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/VSSDK-Analyzersword for word, first seen Nov 8, 2026
- microsoft/vs-streamjsonrpcword for word, first seen Jul 13, 2026
- microsoft/vs-validationword for word, first seen Jul 13, 2026
Other versions3 projects use a version of this.
Word for word · 3
- microsoft/vs-streamjsonrpc★ 943100% same
- microsoft/vs-validation★ 144100% same
- microsoft/VSSDK-Analyzers★ 56100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- bundle-dependency-prsSkill
- testingSkill
- update-library-templateSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Run the .github/Prime-ForCopilot.ps1 script (once) before running any dotnet or msbuild commands.
- Distinctive: line 7
If you see any build errors about not finding git objects or a shallow clone, it may be time to run this script again.
- Very specific: line 12
Avoid introducing binary breaking changes in public APIs of projects under src unless their project files have IsPackable set to false.
- Very specific: line 18
Add API doc comments to all new public and internal members in shipping code under src.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot instructions for this repository
High level guidance
- Review the
CONTRIBUTING.mdfile for instructions to build and test the software. - Run the
.github/Prime-ForCopilot.ps1script (once) before running anydotnetormsbuildcommands. If you see any build errors about not finding git objects or a shallow clone, it may be time to run this script again.
Software Design
- Design APIs to be highly testable, and all functionality should be tested.
- Avoid introducing binary breaking changes in public APIs of projects under
srcunless their project files haveIsPackableset tofalse.
Coding style
- Honor StyleCop rules and fix any reported build warnings after getting tests to pass.
- In C# files, use namespace statements instead of namespace blocks for all new files.
- Add API doc comments to all new public and internal members in shipping code under
src. Tests and samples do not require XML API documentation; do not add XML docs to test or sample members solely to satisfy this rule.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

