Lint

---
name: lint
description: "This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'."
---

# Lint

Health-check wiki structure and surface review candidates. A lint finding is not a verdict that historical intent binds current work; semantic accuracy requires checking implementation/tests and current user direction with `resolve-drift`.

## Steps

**1. Load the index.**

Read the field-guide index. Prefer `.lore/reference/index.md`; if it does not exist, read `.lore/reference/index.html`. Collect every local page link it lists — these are the indexed pages. Links may point to `.md` or `.html` files. If no index exists or the index contains no links, report that and stop.

**2. Run five checks.**

Run all five checks before reporting. Each check has a defined severity; do not promote or demote.

---

### [error] Contradictions

Read every indexed wiki page in full. Pages may be Markdown or HTML. For HTML pages, use meta tags as metadata and visible body content as the page body. Look for pages that make conflicting claims about the same concept, entity, or decision. Two pages contradict each other when they assert incompatible facts about the same subject — not merely when they discuss it differently or at different levels of detail.

For each contradiction found, record:
- Both page paths
- The specific claim each page makes
- The subject they disagree on

---

### [warning] Orphans

List every `.md` and `.html` file under `.lore/reference/`, recursively — stratified wikis keep pages in category subdirectories. Exclude `index.md` and `index.html`. Any file not listed in the index is an orphan.

For each orphan, record its path.

---

### [info] Changed or missing provenance

For each indexed wiki page, read its source metadata. Markdown pages use the `fg-sources` frontmatter field as a YAML list of relative paths. HTML pages use the `fg-sources` meta tag as a comma-separated or YAML-like list.

For each source path:
1. Check whether the file exists on the filesystem.
2. If it exists, its newer modification time may suggest a review, but is not evidence that the reference page is stale. Historical source edits do not establish current behavior.

For each page with a newer provenance source, report it only as an optional review lead; do not change `fg-status` from modification time alone. A source timestamp is provenance, not proof of semantic drift. Use `resolve-drift` to check current claims against code/tests and current user direction.

If a source file no longer exists, report missing provenance as information, not a defect: sources may be deleted after distillation and provenance is not authority.

---

### [info] Stratification due

Count the pages directly inside each directory under `.lore/reference/`, including the root itself (`index.*` and dotfiles don't count; pages in deeper subdirectories count toward their own directory, not the parent). Flag any directory holding more than ~12 pages.

For each flagged directory, record its path and page count, and suggest running `/field-guide:stratify`.

---

### [info] Missing concept pages

Scan all indexed wiki page bodies for terms that appear across multiple pages. A term is a candidate if it recurs in at least two pages and has no dedicated page with `fg-type` set to `concept`. Read `fg-type` from Markdown frontmatter or HTML meta tags.

Flag all candidates found.

For each candidate, record the term and which pages reference it.

---

**3. Produce the report.**

Group findings by severity in this order: errors, warnings, info. Within each group, list findings individually with enough detail to act on them.

Format:

```
[error] Contradiction
  Pages: .lore/reference/auth-decision.md, .lore/reference/auth-architecture.md
  Subject: whether JWT tokens are stateless
  Claim A: "tokens are stateless and require no server-side storage"
  Claim B: "tokens are validated against a server-side revocation list"

[warning] Orphan
  Path: .lore/reference/old-spike.md

[info] Changed provenance (optional review lead)
  Page: .lore/reference/auth-decision.md
  Newer source: .lore/work/retros/auth-rollout.md

[info] Missing provenance
  Page: .lore/reference/deploy-config.md
  Missing: .lore/work/specs/deploy-spec.md

[info] Stratification due
  Directory: .lore/reference/ (17 pages)
  Suggestion: run /field-guide:stratify

[info] Missing concept page
  Term: "revocation list"
  Referenced in: .lore/reference/auth-decision.md, .lore/reference/auth-architecture.md, .lore/reference/session-management.md
```

If a severity bucket is empty, omit it. If no findings at all, say so.

Close with a one-line count: `N errors, N warnings, N info`.