RDF/XML serialization is deferred.
{
"@context": {
"schema": "https://schema.org/",
"wiki": "https://wazootech.github.io/wiki/",
"foaf": "http://xmlns.com/foaf/0.1/",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"xsd": "http://www.w3.org/2001/XMLSchema#",
"owl": "http://www.w3.org/2002/07/owl#",
"dc": "http://purl.org/dc/elements/1.1/",
"dcterms": "http://purl.org/dc/terms/",
"sh": "http://www.w3.org/ns/shacl#",
"wazoo": "https://schema.wazoo.dev/"
},
"@id": "wiki:wiki_lint",
"@type": "schema:TechArticle",
"schema:articleBody": "# `wiki lint`\n\nRun **convention** audits on the wiki: broken links, filename pattern, heading style, and internal link style.\n\n`wiki lint` is a Wiki-policy audit, not a general Markdown linter. Its distinctive checks depend on resolved Wiki routes, cross-page links, `wiki:` CURIEs, and per-rule `wiki.yaml` severity.\n\nWhen `lint.heading_levels` or `lint.duplicate_headings` is enabled, Wiki runs the in-process ESLint Markdown adapter with `@eslint/markdown`'s `markdown/heading-increment` and `markdown/no-duplicate-headings` rules. It maps those diagnostics into Wiki's existing issue codes and severity report without an external ESLint config or subprocess. Wiki keeps the duplicate rule's H2+ scope and heading normalization, along with broken-link resolution, `wiki:` CURIEs, filename rules, editorial heading style, Setext-aware thematic-break checks, and link style. Mechanical formatting remains `wiki fmt`'s job through dprint.\n\nExits **0 silently** on success unless `-v` is set. See [Design Philosophies](Design_Philosophies.md).\n\n## Usage\n\n```bash\nwiki lint\nwiki lint wiki/Some_Page.md\nwiki lint wiki/A.md wiki/B.md\nwiki lint -v\nwiki lint --strict\n```\n\n## Options\n\n| Flag | Description |\n| ----------------- | ---------------------------------------------- |\n| `FILE...` | Optional markdown paths; otherwise entire wiki |\n| `-v`, `--verbose` | Print warnings |\n| `--strict` | Treat warnings as errors (exit 1) |\n\n## What is linted\n\n### Configurable (`lint.*` in `wiki.yaml`)\n\n| Rule key | What it audits |\n| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `broken_links` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs |\n| `filename_pattern` | Full filename vs `wiki.filename_pattern` regex (`.md` files only) |\n| `headings` | Sentence-case H2+ (H1 title case conventional), numbered headings (ATX syntax is **`wiki fmt`**) |\n| `heading_levels` | Heading depth must increase by one level at a time (`@eslint/markdown`'s `markdown/heading-increment`) |\n| `duplicate_headings` | Duplicate H2+ heading text in the same document (`@eslint/markdown`'s `markdown/no-duplicate-headings`, MD024-inspired) |\n| `thematic_breaks` | Horizontal rules (`---`, `***`, `___`) in body prose |\n| `link_style` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard` |\n| `redundant_frontmatter` | A `headline`, `dateCreated`, or `dateModified` that exactly repeats the value the graph derives from the first H1 or Git history ([wiki fix](wiki_fix.md)) |\n\nEach rule is `error`, `warning`, or `off`. Defaults: `broken_links`, `filename_pattern`, and `link_style` are `warning`; `headings`, `heading_levels`, `duplicate_headings`, `thematic_breaks`, and `redundant_frontmatter` are `off`.\n\n`redundant_frontmatter` reports only exact repeats; a differing value is an intentional override and is never reported. It is off by default because a wiki that follows the common convention of repeating the H1 as `headline` would otherwise warn on nearly every page, and fail `--strict`. Remove the repeats with [wiki fix](wiki_fix.md) `--apply`, then enable the rule to keep them out.\n\n`wiki lint` reports broken links only — it does not repair them. Use [wiki link](wiki_link.md) `--fix-broken` for unambiguous repairs (rename map, unique fuzzy slug, or heading match).\n\nRoute safety errors (spaces, unsafe URL characters) abort lint with errors before convention rules run.\n\n### Single-file mode\n\n`wiki lint path/to/Page.md` runs broken-link, filename, heading, and link-style audits for that route only.\n\n## Related CI commands\n\n| Command | Purpose |\n| --------------------- | ----------------------------------------------------------------------------- |\n| `wiki fmt --check` | Deno/dprint Markdown formatter consistency using native inline `fmt:` options |\n| `wiki lint --strict` | Conventions (`lint:` in yaml) |\n| `wiki check --strict` | SHACL, JSON Schema frontmatter, route safety, layout frontmatter |\n| `wiki render --check` | Stale inline SPARQL result blocks |\n\nRun in that order in CI: `fmt`, then `lint`, then `check` — so mechanical fixes land before conventions and integrity checks.\n\n`wiki build` runs `wiki lint` then `wiki check` before writing output unless `--no-check`.\n\n## Related\n\n- [Wiki Configuration](Wiki_Configuration.md) — `lint.*` severities and config semantics\n- [wiki check](wiki_check.md) — integrity lane\n- [Style Guide](Style_Guide.md)",
"schema:dateCreated": {
"@type": "xsd:dateTime",
"@value": "2026-10-31T23:19:03Z"
},
"schema:dateModified": {
"@type": "xsd:dateTime",
"@value": "2026-10-31T23:19:03Z"
},
"schema:description": "Convention audits for broken links, filename patterns, heading style, and internal link style.",
"schema:headline": "wiki lint"
}
@prefix schema: <https://schema.org/>.
@prefix wiki: <https://wazootech.github.io/wiki/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix sh: <http://www.w3.org/ns/shacl#>.
@prefix wazoo: <https://schema.wazoo.dev/>.
wiki:wiki_lint a schema:TechArticle;
schema:description "Convention audits for broken links, filename patterns, heading style, and internal link style.";
schema:articleBody "# `wiki lint`\n\nRun **convention** audits on the wiki: broken links, filename pattern, heading style, and internal link style.\n\n`wiki lint` is a Wiki-policy audit, not a general Markdown linter. Its distinctive checks depend on resolved Wiki routes, cross-page links, `wiki:` CURIEs, and per-rule `wiki.yaml` severity.\n\nWhen `lint.heading_levels` or `lint.duplicate_headings` is enabled, Wiki runs the in-process ESLint Markdown adapter with `@eslint/markdown`'s `markdown/heading-increment` and `markdown/no-duplicate-headings` rules. It maps those diagnostics into Wiki's existing issue codes and severity report without an external ESLint config or subprocess. Wiki keeps the duplicate rule's H2+ scope and heading normalization, along with broken-link resolution, `wiki:` CURIEs, filename rules, editorial heading style, Setext-aware thematic-break checks, and link style. Mechanical formatting remains `wiki fmt`'s job through dprint.\n\nExits **0 silently** on success unless `-v` is set. See [Design Philosophies](Design_Philosophies.md).\n\n## Usage\n\n```bash\nwiki lint\nwiki lint wiki/Some_Page.md\nwiki lint wiki/A.md wiki/B.md\nwiki lint -v\nwiki lint --strict\n```\n\n## Options\n\n| Flag | Description |\n| ----------------- | ---------------------------------------------- |\n| `FILE...` | Optional markdown paths; otherwise entire wiki |\n| `-v`, `--verbose` | Print warnings |\n| `--strict` | Treat warnings as errors (exit 1) |\n\n## What is linted\n\n### Configurable (`lint.*` in `wiki.yaml`)\n\n| Rule key | What it audits |\n| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `broken_links` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs |\n| `filename_pattern` | Full filename vs `wiki.filename_pattern` regex (`.md` files only) |\n| `headings` | Sentence-case H2+ (H1 title case conventional), numbered headings (ATX syntax is **`wiki fmt`**) |\n| `heading_levels` | Heading depth must increase by one level at a time (`@eslint/markdown`'s `markdown/heading-increment`) |\n| `duplicate_headings` | Duplicate H2+ heading text in the same document (`@eslint/markdown`'s `markdown/no-duplicate-headings`, MD024-inspired) |\n| `thematic_breaks` | Horizontal rules (`---`, `***`, `___`) in body prose |\n| `link_style` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard` |\n| `redundant_frontmatter` | A `headline`, `dateCreated`, or `dateModified` that exactly repeats the value the graph derives from the first H1 or Git history ([wiki fix](wiki_fix.md)) |\n\nEach rule is `error`, `warning`, or `off`. Defaults: `broken_links`, `filename_pattern`, and `link_style` are `warning`; `headings`, `heading_levels`, `duplicate_headings`, `thematic_breaks`, and `redundant_frontmatter` are `off`.\n\n`redundant_frontmatter` reports only exact repeats; a differing value is an intentional override and is never reported. It is off by default because a wiki that follows the common convention of repeating the H1 as `headline` would otherwise warn on nearly every page, and fail `--strict`. Remove the repeats with [wiki fix](wiki_fix.md) `--apply`, then enable the rule to keep them out.\n\n`wiki lint` reports broken links only — it does not repair them. Use [wiki link](wiki_link.md) `--fix-broken` for unambiguous repairs (rename map, unique fuzzy slug, or heading match).\n\nRoute safety errors (spaces, unsafe URL characters) abort lint with errors before convention rules run.\n\n### Single-file mode\n\n`wiki lint path/to/Page.md` runs broken-link, filename, heading, and link-style audits for that route only.\n\n## Related CI commands\n\n| Command | Purpose |\n| --------------------- | ----------------------------------------------------------------------------- |\n| `wiki fmt --check` | Deno/dprint Markdown formatter consistency using native inline `fmt:` options |\n| `wiki lint --strict` | Conventions (`lint:` in yaml) |\n| `wiki check --strict` | SHACL, JSON Schema frontmatter, route safety, layout frontmatter |\n| `wiki render --check` | Stale inline SPARQL result blocks |\n\nRun in that order in CI: `fmt`, then `lint`, then `check` — so mechanical fixes land before conventions and integrity checks.\n\n`wiki build` runs `wiki lint` then `wiki check` before writing output unless `--no-check`.\n\n## Related\n\n- [Wiki Configuration](Wiki_Configuration.md) — `lint.*` severities and config semantics\n- [wiki check](wiki_check.md) — integrity lane\n- [Style Guide](Style_Guide.md)";
schema:headline "wiki lint";
schema:dateCreated "2026-10-31T23:19:03Z"^^xsd:dateTime;
schema:dateModified "2026-10-31T23:19:03Z"^^xsd:dateTime.
@prefix schema: <https://schema.org/>.
@prefix wiki: <https://wazootech.github.io/wiki/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix sh: <http://www.w3.org/ns/shacl#>.
@prefix wazoo: <https://schema.wazoo.dev/>.
wiki:wiki_lint a schema:TechArticle;
schema:description "Convention audits for broken links, filename patterns, heading style, and internal link style.";
schema:articleBody "# `wiki lint`\n\nRun **convention** audits on the wiki: broken links, filename pattern, heading style, and internal link style.\n\n`wiki lint` is a Wiki-policy audit, not a general Markdown linter. Its distinctive checks depend on resolved Wiki routes, cross-page links, `wiki:` CURIEs, and per-rule `wiki.yaml` severity.\n\nWhen `lint.heading_levels` or `lint.duplicate_headings` is enabled, Wiki runs the in-process ESLint Markdown adapter with `@eslint/markdown`'s `markdown/heading-increment` and `markdown/no-duplicate-headings` rules. It maps those diagnostics into Wiki's existing issue codes and severity report without an external ESLint config or subprocess. Wiki keeps the duplicate rule's H2+ scope and heading normalization, along with broken-link resolution, `wiki:` CURIEs, filename rules, editorial heading style, Setext-aware thematic-break checks, and link style. Mechanical formatting remains `wiki fmt`'s job through dprint.\n\nExits **0 silently** on success unless `-v` is set. See [Design Philosophies](Design_Philosophies.md).\n\n## Usage\n\n```bash\nwiki lint\nwiki lint wiki/Some_Page.md\nwiki lint wiki/A.md wiki/B.md\nwiki lint -v\nwiki lint --strict\n```\n\n## Options\n\n| Flag | Description |\n| ----------------- | ---------------------------------------------- |\n| `FILE...` | Optional markdown paths; otherwise entire wiki |\n| `-v`, `--verbose` | Print warnings |\n| `--strict` | Treat warnings as errors (exit 1) |\n\n## What is linted\n\n### Configurable (`lint.*` in `wiki.yaml`)\n\n| Rule key | What it audits |\n| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `broken_links` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs |\n| `filename_pattern` | Full filename vs `wiki.filename_pattern` regex (`.md` files only) |\n| `headings` | Sentence-case H2+ (H1 title case conventional), numbered headings (ATX syntax is **`wiki fmt`**) |\n| `heading_levels` | Heading depth must increase by one level at a time (`@eslint/markdown`'s `markdown/heading-increment`) |\n| `duplicate_headings` | Duplicate H2+ heading text in the same document (`@eslint/markdown`'s `markdown/no-duplicate-headings`, MD024-inspired) |\n| `thematic_breaks` | Horizontal rules (`---`, `***`, `___`) in body prose |\n| `link_style` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard` |\n| `redundant_frontmatter` | A `headline`, `dateCreated`, or `dateModified` that exactly repeats the value the graph derives from the first H1 or Git history ([wiki fix](wiki_fix.md)) |\n\nEach rule is `error`, `warning`, or `off`. Defaults: `broken_links`, `filename_pattern`, and `link_style` are `warning`; `headings`, `heading_levels`, `duplicate_headings`, `thematic_breaks`, and `redundant_frontmatter` are `off`.\n\n`redundant_frontmatter` reports only exact repeats; a differing value is an intentional override and is never reported. It is off by default because a wiki that follows the common convention of repeating the H1 as `headline` would otherwise warn on nearly every page, and fail `--strict`. Remove the repeats with [wiki fix](wiki_fix.md) `--apply`, then enable the rule to keep them out.\n\n`wiki lint` reports broken links only — it does not repair them. Use [wiki link](wiki_link.md) `--fix-broken` for unambiguous repairs (rename map, unique fuzzy slug, or heading match).\n\nRoute safety errors (spaces, unsafe URL characters) abort lint with errors before convention rules run.\n\n### Single-file mode\n\n`wiki lint path/to/Page.md` runs broken-link, filename, heading, and link-style audits for that route only.\n\n## Related CI commands\n\n| Command | Purpose |\n| --------------------- | ----------------------------------------------------------------------------- |\n| `wiki fmt --check` | Deno/dprint Markdown formatter consistency using native inline `fmt:` options |\n| `wiki lint --strict` | Conventions (`lint:` in yaml) |\n| `wiki check --strict` | SHACL, JSON Schema frontmatter, route safety, layout frontmatter |\n| `wiki render --check` | Stale inline SPARQL result blocks |\n\nRun in that order in CI: `fmt`, then `lint`, then `check` — so mechanical fixes land before conventions and integrity checks.\n\n`wiki build` runs `wiki lint` then `wiki check` before writing output unless `--no-check`.\n\n## Related\n\n- [Wiki Configuration](Wiki_Configuration.md) — `lint.*` severities and config semantics\n- [wiki check](wiki_check.md) — integrity lane\n- [Style Guide](Style_Guide.md)";
schema:headline "wiki lint";
schema:dateCreated "2026-10-31T23:19:03Z"^^xsd:dateTime;
schema:dateModified "2026-10-31T23:19:03Z"^^xsd:dateTime.
<https://wazootech.github.io/wiki/wiki_lint> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/TechArticle> .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/description> "Convention audits for broken links, filename patterns, heading style, and internal link style." .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/articleBody> "# `wiki lint`\n\nRun **convention** audits on the wiki: broken links, filename pattern, heading style, and internal link style.\n\n`wiki lint` is a Wiki-policy audit, not a general Markdown linter. Its distinctive checks depend on resolved Wiki routes, cross-page links, `wiki:` CURIEs, and per-rule `wiki.yaml` severity.\n\nWhen `lint.heading_levels` or `lint.duplicate_headings` is enabled, Wiki runs the in-process ESLint Markdown adapter with `@eslint/markdown`'s `markdown/heading-increment` and `markdown/no-duplicate-headings` rules. It maps those diagnostics into Wiki's existing issue codes and severity report without an external ESLint config or subprocess. Wiki keeps the duplicate rule's H2+ scope and heading normalization, along with broken-link resolution, `wiki:` CURIEs, filename rules, editorial heading style, Setext-aware thematic-break checks, and link style. Mechanical formatting remains `wiki fmt`'s job through dprint.\n\nExits **0 silently** on success unless `-v` is set. See [Design Philosophies](Design_Philosophies.md).\n\n## Usage\n\n```bash\nwiki lint\nwiki lint wiki/Some_Page.md\nwiki lint wiki/A.md wiki/B.md\nwiki lint -v\nwiki lint --strict\n```\n\n## Options\n\n| Flag | Description |\n| ----------------- | ---------------------------------------------- |\n| `FILE...` | Optional markdown paths; otherwise entire wiki |\n| `-v`, `--verbose` | Print warnings |\n| `--strict` | Treat warnings as errors (exit 1) |\n\n## What is linted\n\n### Configurable (`lint.*` in `wiki.yaml`)\n\n| Rule key | What it audits |\n| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `broken_links` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs |\n| `filename_pattern` | Full filename vs `wiki.filename_pattern` regex (`.md` files only) |\n| `headings` | Sentence-case H2+ (H1 title case conventional), numbered headings (ATX syntax is **`wiki fmt`**) |\n| `heading_levels` | Heading depth must increase by one level at a time (`@eslint/markdown`'s `markdown/heading-increment`) |\n| `duplicate_headings` | Duplicate H2+ heading text in the same document (`@eslint/markdown`'s `markdown/no-duplicate-headings`, MD024-inspired) |\n| `thematic_breaks` | Horizontal rules (`---`, `***`, `___`) in body prose |\n| `link_style` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard` |\n| `redundant_frontmatter` | A `headline`, `dateCreated`, or `dateModified` that exactly repeats the value the graph derives from the first H1 or Git history ([wiki fix](wiki_fix.md)) |\n\nEach rule is `error`, `warning`, or `off`. Defaults: `broken_links`, `filename_pattern`, and `link_style` are `warning`; `headings`, `heading_levels`, `duplicate_headings`, `thematic_breaks`, and `redundant_frontmatter` are `off`.\n\n`redundant_frontmatter` reports only exact repeats; a differing value is an intentional override and is never reported. It is off by default because a wiki that follows the common convention of repeating the H1 as `headline` would otherwise warn on nearly every page, and fail `--strict`. Remove the repeats with [wiki fix](wiki_fix.md) `--apply`, then enable the rule to keep them out.\n\n`wiki lint` reports broken links only — it does not repair them. Use [wiki link](wiki_link.md) `--fix-broken` for unambiguous repairs (rename map, unique fuzzy slug, or heading match).\n\nRoute safety errors (spaces, unsafe URL characters) abort lint with errors before convention rules run.\n\n### Single-file mode\n\n`wiki lint path/to/Page.md` runs broken-link, filename, heading, and link-style audits for that route only.\n\n## Related CI commands\n\n| Command | Purpose |\n| --------------------- | ----------------------------------------------------------------------------- |\n| `wiki fmt --check` | Deno/dprint Markdown formatter consistency using native inline `fmt:` options |\n| `wiki lint --strict` | Conventions (`lint:` in yaml) |\n| `wiki check --strict` | SHACL, JSON Schema frontmatter, route safety, layout frontmatter |\n| `wiki render --check` | Stale inline SPARQL result blocks |\n\nRun in that order in CI: `fmt`, then `lint`, then `check` — so mechanical fixes land before conventions and integrity checks.\n\n`wiki build` runs `wiki lint` then `wiki check` before writing output unless `--no-check`.\n\n## Related\n\n- [Wiki Configuration](Wiki_Configuration.md) — `lint.*` severities and config semantics\n- [wiki check](wiki_check.md) — integrity lane\n- [Style Guide](Style_Guide.md)" .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/headline> "wiki lint" .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/dateCreated> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/dateModified> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
@prefix schema: <https://schema.org/>.
@prefix wiki: <https://wazootech.github.io/wiki/>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix sh: <http://www.w3.org/ns/shacl#>.
@prefix wazoo: <https://schema.wazoo.dev/>.
wiki:wiki_lint a schema:TechArticle;
schema:description "Convention audits for broken links, filename patterns, heading style, and internal link style.";
schema:articleBody "# `wiki lint`\n\nRun **convention** audits on the wiki: broken links, filename pattern, heading style, and internal link style.\n\n`wiki lint` is a Wiki-policy audit, not a general Markdown linter. Its distinctive checks depend on resolved Wiki routes, cross-page links, `wiki:` CURIEs, and per-rule `wiki.yaml` severity.\n\nWhen `lint.heading_levels` or `lint.duplicate_headings` is enabled, Wiki runs the in-process ESLint Markdown adapter with `@eslint/markdown`'s `markdown/heading-increment` and `markdown/no-duplicate-headings` rules. It maps those diagnostics into Wiki's existing issue codes and severity report without an external ESLint config or subprocess. Wiki keeps the duplicate rule's H2+ scope and heading normalization, along with broken-link resolution, `wiki:` CURIEs, filename rules, editorial heading style, Setext-aware thematic-break checks, and link style. Mechanical formatting remains `wiki fmt`'s job through dprint.\n\nExits **0 silently** on success unless `-v` is set. See [Design Philosophies](Design_Philosophies.md).\n\n## Usage\n\n```bash\nwiki lint\nwiki lint wiki/Some_Page.md\nwiki lint wiki/A.md wiki/B.md\nwiki lint -v\nwiki lint --strict\n```\n\n## Options\n\n| Flag | Description |\n| ----------------- | ---------------------------------------------- |\n| `FILE...` | Optional markdown paths; otherwise entire wiki |\n| `-v`, `--verbose` | Print warnings |\n| `--strict` | Treat warnings as errors (exit 1) |\n\n## What is linted\n\n### Configurable (`lint.*` in `wiki.yaml`)\n\n| Rule key | What it audits |\n| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `broken_links` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs |\n| `filename_pattern` | Full filename vs `wiki.filename_pattern` regex (`.md` files only) |\n| `headings` | Sentence-case H2+ (H1 title case conventional), numbered headings (ATX syntax is **`wiki fmt`**) |\n| `heading_levels` | Heading depth must increase by one level at a time (`@eslint/markdown`'s `markdown/heading-increment`) |\n| `duplicate_headings` | Duplicate H2+ heading text in the same document (`@eslint/markdown`'s `markdown/no-duplicate-headings`, MD024-inspired) |\n| `thematic_breaks` | Horizontal rules (`---`, `***`, `___`) in body prose |\n| `link_style` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard` |\n| `redundant_frontmatter` | A `headline`, `dateCreated`, or `dateModified` that exactly repeats the value the graph derives from the first H1 or Git history ([wiki fix](wiki_fix.md)) |\n\nEach rule is `error`, `warning`, or `off`. Defaults: `broken_links`, `filename_pattern`, and `link_style` are `warning`; `headings`, `heading_levels`, `duplicate_headings`, `thematic_breaks`, and `redundant_frontmatter` are `off`.\n\n`redundant_frontmatter` reports only exact repeats; a differing value is an intentional override and is never reported. It is off by default because a wiki that follows the common convention of repeating the H1 as `headline` would otherwise warn on nearly every page, and fail `--strict`. Remove the repeats with [wiki fix](wiki_fix.md) `--apply`, then enable the rule to keep them out.\n\n`wiki lint` reports broken links only — it does not repair them. Use [wiki link](wiki_link.md) `--fix-broken` for unambiguous repairs (rename map, unique fuzzy slug, or heading match).\n\nRoute safety errors (spaces, unsafe URL characters) abort lint with errors before convention rules run.\n\n### Single-file mode\n\n`wiki lint path/to/Page.md` runs broken-link, filename, heading, and link-style audits for that route only.\n\n## Related CI commands\n\n| Command | Purpose |\n| --------------------- | ----------------------------------------------------------------------------- |\n| `wiki fmt --check` | Deno/dprint Markdown formatter consistency using native inline `fmt:` options |\n| `wiki lint --strict` | Conventions (`lint:` in yaml) |\n| `wiki check --strict` | SHACL, JSON Schema frontmatter, route safety, layout frontmatter |\n| `wiki render --check` | Stale inline SPARQL result blocks |\n\nRun in that order in CI: `fmt`, then `lint`, then `check` — so mechanical fixes land before conventions and integrity checks.\n\n`wiki build` runs `wiki lint` then `wiki check` before writing output unless `--no-check`.\n\n## Related\n\n- [Wiki Configuration](Wiki_Configuration.md) — `lint.*` severities and config semantics\n- [wiki check](wiki_check.md) — integrity lane\n- [Style Guide](Style_Guide.md)";
schema:headline "wiki lint";
schema:dateCreated "2026-10-31T23:19:03Z"^^xsd:dateTime;
schema:dateModified "2026-10-31T23:19:03Z"^^xsd:dateTime.
<https://wazootech.github.io/wiki/wiki_lint> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/TechArticle> .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/description> "Convention audits for broken links, filename patterns, heading style, and internal link style." .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/articleBody> """# `wiki lint`
Run **convention** audits on the wiki: broken links, filename pattern, heading style, and internal link style.
`wiki lint` is a Wiki-policy audit, not a general Markdown linter. Its distinctive checks depend on resolved Wiki routes, cross-page links, `wiki:` CURIEs, and per-rule `wiki.yaml` severity.
When `lint.heading_levels` or `lint.duplicate_headings` is enabled, Wiki runs the in-process ESLint Markdown adapter with `@eslint/markdown`'s `markdown/heading-increment` and `markdown/no-duplicate-headings` rules. It maps those diagnostics into Wiki's existing issue codes and severity report without an external ESLint config or subprocess. Wiki keeps the duplicate rule's H2+ scope and heading normalization, along with broken-link resolution, `wiki:` CURIEs, filename rules, editorial heading style, Setext-aware thematic-break checks, and link style. Mechanical formatting remains `wiki fmt`'s job through dprint.
Exits **0 silently** on success unless `-v` is set. See [Design Philosophies](Design_Philosophies.md).
## Usage
```bash
wiki lint
wiki lint wiki/Some_Page.md
wiki lint wiki/A.md wiki/B.md
wiki lint -v
wiki lint --strict
```
## Options
| Flag | Description |
| ----------------- | ---------------------------------------------- |
| `FILE...` | Optional markdown paths; otherwise entire wiki |
| `-v`, `--verbose` | Print warnings |
| `--strict` | Treat warnings as errors (exit 1) |
## What is linted
### Configurable (`lint.*` in `wiki.yaml`)
| Rule key | What it audits |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `broken_links` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs |
| `filename_pattern` | Full filename vs `wiki.filename_pattern` regex (`.md` files only) |
| `headings` | Sentence-case H2+ (H1 title case conventional), numbered headings (ATX syntax is **`wiki fmt`**) |
| `heading_levels` | Heading depth must increase by one level at a time (`@eslint/markdown`'s `markdown/heading-increment`) |
| `duplicate_headings` | Duplicate H2+ heading text in the same document (`@eslint/markdown`'s `markdown/no-duplicate-headings`, MD024-inspired) |
| `thematic_breaks` | Horizontal rules (`---`, `***`, `___`) in body prose |
| `link_style` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard` |
| `redundant_frontmatter` | A `headline`, `dateCreated`, or `dateModified` that exactly repeats the value the graph derives from the first H1 or Git history ([wiki fix](wiki_fix.md)) |
Each rule is `error`, `warning`, or `off`. Defaults: `broken_links`, `filename_pattern`, and `link_style` are `warning`; `headings`, `heading_levels`, `duplicate_headings`, `thematic_breaks`, and `redundant_frontmatter` are `off`.
`redundant_frontmatter` reports only exact repeats; a differing value is an intentional override and is never reported. It is off by default because a wiki that follows the common convention of repeating the H1 as `headline` would otherwise warn on nearly every page, and fail `--strict`. Remove the repeats with [wiki fix](wiki_fix.md) `--apply`, then enable the rule to keep them out.
`wiki lint` reports broken links only — it does not repair them. Use [wiki link](wiki_link.md) `--fix-broken` for unambiguous repairs (rename map, unique fuzzy slug, or heading match).
Route safety errors (spaces, unsafe URL characters) abort lint with errors before convention rules run.
### Single-file mode
`wiki lint path/to/Page.md` runs broken-link, filename, heading, and link-style audits for that route only.
## Related CI commands
| Command | Purpose |
| --------------------- | ----------------------------------------------------------------------------- |
| `wiki fmt --check` | Deno/dprint Markdown formatter consistency using native inline `fmt:` options |
| `wiki lint --strict` | Conventions (`lint:` in yaml) |
| `wiki check --strict` | SHACL, JSON Schema frontmatter, route safety, layout frontmatter |
| `wiki render --check` | Stale inline SPARQL result blocks |
Run in that order in CI: `fmt`, then `lint`, then `check` — so mechanical fixes land before conventions and integrity checks.
`wiki build` runs `wiki lint` then `wiki check` before writing output unless `--no-check`.
## Related
- [Wiki Configuration](Wiki_Configuration.md) — `lint.*` severities and config semantics
- [wiki check](wiki_check.md) — integrity lane
- [Style Guide](Style_Guide.md)""" .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/headline> "wiki lint" .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/dateCreated> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
<https://wazootech.github.io/wiki/wiki_lint> <https://schema.org/dateModified> "2026-10-31T23:19:03Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .