Audit freshness
Report what's stale. This skill never edits content. Version drift goes to refresh-dotnet-versions, and content drift goes to harvest-sources.
Tolerances
| Check | Tolerance |
|---|---|
last-reviewed on any opinions/ file |
180 days |
last-reviewed after a new major .NET release ships |
60 days from the release |
targets: against the latest released .NET, C#, and F# |
Zero: any lag is a finding |
last-reviewed on any commented templates/ header |
180 days |
sdk.version in global.json and templates/global.json |
Checked for shape, not band lag. For details, see SDK pins |
<PackageVersion> pins in templates/Directory.Packages.props against nuget.org |
One minor version, or any major version. Patch-only drift is informational |
The Versions verified against nuget.org … on <date> comment in the same file |
90 days, because the pins change faster than the prose |
research/ topics |
90 days, then reported for resolve-research. For details, see Research |
sources: IDs |
For the rules, see Sources |
**Review by YYYY-MM-DD.** markings in opinions/ and templates/ |
Zero past the date. Report each for drop-or-re-date triage |
Inbound references to each opinions/ and templates/ file |
Informational, never a finding. For details, see References |
templates/ still implement what opinions/ require |
Zero. For details, see Templates |
templates/ build and test without errors |
Zero. For details, see Templates |
| Citation and roster URLs resolve | Zero: a dead link is a content finding. Read the latest Markdown workflow run, not each URL |
SDK pins
The SDK pin is a minimum, and latestFeature picks up newer bands without an edit (refresh-dotnet-versions, step 4a). Don't report how far the pin trails the latest band. Report these instead:
- A patch-level pin where a band minimum belongs, such as
10.0.412instead of10.0.400. - A
rollForwardthat's missing or narrower thanlatestFeature. - A minimum whose major and minor version don't match
targets:.
Research
Every topic on disk is unresolved, so all of them count. A topic still on disk after promotion is a finding, because promotion ends in deletion.
Sources
- In an opinion or template, every ID must resolve to a Citable row in
AWESOME-HUMANS.md, or be a reservedhouse:<profile>ID. - A
house:<profile>ID is never a finding, in any directory. - In an opinion or template, a watch-list ID or a
**Discovery-only.**ID is a finding. So is a file whose citable sources are all marked**Corroborate.**.scripts/validate-sources.csalready fails the build on all three. research/topics can name unvetted sources if the text flags them, but never an opted-out one, because its owner asked not to be cited at all.scripts/validate-sources.csdoesn't checkresearch/, so report an opted-out ID there.
References
Count what refers to each opinion and template, by link or by file name, from the repository itself: skills/, AGENTS.md, HOUSE-OPINIONS.md, the other opinions, the template comments, and research/ topics. Leave out the README.md Scope bullets and layout tree, because every opinion appears there.
Report each file with no inbound references as a pruning candidate. Nothing on the web or in another project shows up here, so a file with no references might still be read. Never report it as stale on that count alone.
Templates
- Templates match the opinions. If an opinion names a property, package, or setting, and its template leaves it out, that's a finding. People copy
templates/, so a gap ships the advice without the setting. - Templates build and test. Assemble the example projects into the layout
example.slnxdescribes, and rundotnet buildanddotnet test. Analyzer and package compatibility failures show up only this way.
Steps
- Collect the metadata from every file under
opinions/andresearch/, and from the comment headers intemplates/:targets,last-reviewed, andsources. Count the inbound references to each opinion and template, as References describes. - Find the latest released versions of .NET, C#, and F#, from the same sources as
refresh-dotnet-versionsstep 1. Find the latest stable version of every package intemplates/Directory.Packages.props, with the lookup inrefresh-dotnet-versionsstep 4b.- Skip SDK band lookups: the
global.jsoncheck reads the pin's shape, not its distance from the newest release. - If you're offline, skip the checks you can't run, and say so in the report. Report an unchecked pin as "not verified", never as fresh.
- Skip SDK band lookups: the
- Evaluate each resource against the tolerances, including any
**Review by YYYY-MM-DD.**marking in its body (AGENTS.md: Writing style for opinions). Missing or malformed metadata is a high-severity finding. - Check the roster. Flag sources in
AWESOME-HUMANS.mdwith no published writing in over a year forvet-sourcere-evaluation. Repository activity doesn't count, because opinions don't cite it. - Write the report, most stale first:
- For each resource: the path, the findings, the days over tolerance, and the skill that fixes it.
- Counts of fresh, stale, and malformed resources, and the oldest
last-revieweddate.
- Recommend next actions, usually
refresh-dotnet-versions,harvest-sources, orresolve-researchfor an overdue topic. Don't run them unless asked.
Edge cases
- A repository with no opinions yet: Report that there's nothing to check. Don't pass.
- House content (
house:<profile>insources:, and that profile's house blocks or regions; see HOUSE-OPINIONS.md): The reserved ID is never an unknown-source finding, and never suggest removing it.scripts/validate-sources.csfails a build where the ID and its blocks don't appear together, or**House:**sits outside a block. Review a house block's age with its file, and never count it as stale sourced text. - Files that can't carry a comment header: The repository-root
global.json, plus exactly twotemplates/files:templates/global.jsonandtemplates/example.slnf. Missing metadata isn't a finding for them. Audit the pinned value against the latest release instead..slnxis XML and carries a header, so it isn't exempt.scripts/validate-metadata.csenforces this two-file list in CI, so any other headerless JSON undertemplates/fails there.
- A package pin held back on purpose, for a known-bad release or a tracked major migration: Report the drift as informational once a comment beside the pin gives the reason. Deliberate staleness must look different from silent staleness.
- A resource that doesn't depend on a version, such as naming conventions: It can declare
targets: [any]. Version checks skip it, and review-age checks still apply. - Clock skew or future dates in the metadata: Report them as malformed.