docs-recheck
Skill1 starsChanged 31 days agoLicence not identifiedView on GitHub
Re-check every documentation claim of this repository against Microsoft's current docs. Use when the user asks to "re-check the docs", "verify the gap analysis", "has Microsoft filled the docs since", "update the documented features", "is X really not documented", or after Microsoft updates the what's new pages for the wave. Refreshes the baseline, has agents compare all features against the full what's new text and the wider Microsoft Learn docs, checks the reverse claims against the transcripts, records the reviewed results in data/release-plan/overrides.json and rebuilds everything with the new check date.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
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.