lode-auditlisted
Install: claude install-skill e128/dotnet-reference
Audit lode/ documentation for content accuracy against the current codebase.
## Phase 0: Resume Check
```bash
cat .claude/tmp/lode-audit/state.md 2>/dev/null
```
If `state.md` exists, load it and skip phases already marked DONE. Otherwise:
```bash
mkdir -p .claude/tmp/lode-audit
```
Initialize `state.md`:
```
# Lode Audit State
Started: {date -u +"%Y-%m-%dT%H:%M:%SZ"}
```
---
## Phase 1: Enumerate Lode Files
Read `lode/lode-map.md` to extract all referenced `.md` file paths. For each path, extract the `*Updated:*` timestamp (format: `YYYY-MM-DDTHH:MM:SSZ`) and record the file path, timestamp (or "no timestamp"), and line count.
Save to `.claude/tmp/lode-audit/files.md`:
```
# Lode Files
| File | Updated | Lines |
|------|---------|-------|
| lode/summary.md | 2026-02-15T00:00:00Z | 42 |
...
```
Write to state.md: `- Phase 1 (Enumerate): DONE — {N} files found -> files.md`
---
## Phase 2: Staleness Assessment
Use `scripts/lode-ts.sh --stale --json` to get a structured staleness report for all lode files in one call. This returns each file's `days_ago` and `commits_since` (commits to src/tests/scripts/.claude since the file's timestamp).
Classification:
- `commits_since > 0` -> **POTENTIALLY STALE**
- No timestamp in file -> **NO TIMESTAMP** (not included in --stale output; check Phase 1 files.md for these)
- `commits_since == 0` -> **CURRENT**
Save to `.claude/tmp/lode-audit/assessment.md`:
```
# Staleness Assessment
| File | Updated | Commits Since | Status |
|