Skip to content

Lambenthan/empiricalwiki / i18n/en/skills/check

Scan the full wiki to detect health issues and produce a tiered fix-recommendation report (covers all 9 entity types + graph consistency)

/check

Scans the full wiki to detect structural, link, field, and graph health issues, and generates a tiered fix-recommendation report. Covers all 9 entity types, including claims confidence plausibility, idea failure-reason completeness, experiment-claim link validity, and graph edge consistency.

Inputs

  • Full wiki directory (default wiki/)
  • Optional: --json flag (output JSON format via tools/lint.py)
  • Optional: --fix flag (auto-fix deterministic issues)
  • Optional: --fix --dry-run (preview fixes without applying them)
  • Optional: --suggest flag (show recommendations for issues that cannot be auto-fixed)

Outputs

  • Lint report (reported directly to the user)
  • Optional file write: wiki/outputs/lint-report-{date}.md

Wiki Interaction

Reads

  • wiki/papers/*.md — paper page fields and links
  • wiki/concepts/*.md — concept page fields and links
  • wiki/topics/*.md — topic page fields and links
  • wiki/people/*.md — people page fields and links
  • wiki/ideas/*.md — idea status, failure_reason, origin_gaps
  • wiki/experiments/*.md — experiment status, target_claim, outcome
  • wiki/claims/*.md — claim confidence, status, evidence, source_papers
  • wiki/Summary/*.md — survey page fields
  • wiki/graph/edges.jsonl — semantic graph edge consistency check
  • wiki/graph/citations.jsonl — bibliographic citation consistency check
  • wiki/index.md — cross-check page completeness

Writes

  • Does not directly modify wiki content (reports only, no fixes)
  • wiki/log.md — records lint result summary via tools/research_wiki.py log

Workflow

Pre-conditions: confirm the working directory is the wiki project root (directory containing wiki/, raw/, tools/). Set WIKI_ROOT=wiki/.

Step 1: Run the Automated Lint Tool

Default mode (report only):

python3 tools/lint.py --wiki-dir wiki/ --json

Auto-fix mode (when user specifies --fix):

python3 tools/lint.py --wiki-dir wiki/ --fix --json

Auto-fixes deterministic issues (xref reverse-link completion, missing fields filled with default values) and outputs a fix report.

Preview mode (when user specifies --fix --dry-run):

python3 tools/lint.py --wiki-dir wiki/ --fix --dry-run --json

Previews what would be fixed without applying any changes.

Parse the JSON output to obtain all automatically detected issues (and fix results).

Step 2: Structural Completeness (automated coverage)

The automated tool checks:

  1. Broken wikilinks: [[slug]] target file does not exist
  2. Orphan pages: pages with no incoming links
  3. Missing required fields (all 9 entity types):
    • papers: title, slug, tags, importance
    • concepts: title, tags, maturity, key_papers
    • topics: title, tags
    • people: name, tags
    • Summary: title, scope, key_topics
    • ideas: title, slug, status, origin, tags, priority
    • experiments: title, slug, status, target_claim, hypothesis, tags
    • claims: title, slug, status, confidence, tags, source_papers, evidence

Step 3: Field Value Validation (automated coverage)

  1. Enum value checks:
    • papers.importance ∈ {1,2,3,4,5}
    • concepts.maturity ∈ {stable, active, emerging, deprecated}
    • ideas.status ∈ {proposed, in_progress, tested, validated, failed}
    • ideas.priority ∈ {1,2,3,4,5}
    • experiments.status ∈ {planned, running, completed, abandoned}
    • experiments.outcome ∈ {succeeded, failed, inconclusive}
    • claims.status ∈ {proposed, weakly_supported, supported, challenged, deprecated}
  2. Claim confidence ∈ [0.0, 1.0]
  3. Idea failure_reason: must be non-empty when status=failed (anti-repetition memory)
  4. Experiment target_claim: the referenced claim must exist

Step 4: Cross Reference Symmetry (automated coverage)

Check all bidirectional link rules defined in CLAUDE.md:

Forward linkReverse link checked
concepts.key_papers → paperspapers.Related contains concept link
papers → people (wikilink)people.Key papers contains paper
claims.source_papers → paperspapers.Related contains claim link
ideas.origin_gaps → claimsclaims.Linked ideas contains idea
experiments.target_claim → claimsclaims.evidence contains experiment

Step 5: Graph Edge Consistency (automated coverage)

  1. JSON format validity: every line is valid JSON
  2. Required fields: each edge has from, to, type
  3. Edge type validity: semantic edges use the current endpoint-aware type sets; legacy paper-paper / paper-concept types produce migration warnings
  4. Edge confidence: /ingest paper-paper and paper-concept semantic edges use confidence: high|medium|low
  5. Citation layer: graph/citations.jsonl rows use type: cites, valid source/date, paper endpoints, and no confidence field
  6. Dangling nodes: wiki pages referenced by from/to must exist

Step 6: Content Quality (LLM-assisted)

Items detectable by the automated tool:

  1. Papers with importance=5 have no concept page referencing them
  2. Concepts with maturity=stable have only 1 key_paper
  3. Topics have empty Open problems sections

Additional LLM judgments (requires reading content):

  1. Concept near-duplicate detection: scan all concept page titles + aliases and assess whether any pairs are semantically identical or highly similar (e.g. "attention mechanism" and "self-attention"). Output merge recommendations for suspected duplicates.
  2. Contradictory statement detection (inconsistent descriptions of the same fact across different pages)
  3. SOTA records not updated in over 6 months
  4. people Recent work not updated in over 6 months
  5. Claim confidence inconsistent with evidence quantity/strength
  6. High-priority idea stuck in proposed status for a long time

Step 7: Generate Report

Output sorted by priority:

## Lint Report — YYYY-MM-DD

**Summary**: N 🔴, M 🟡, K 🔵

### 🔴 Fix Immediately
1. [file] — {issue description}

### 🟡 Recommended Fixes
1. [file] — {issue description}

### 🔵 Optional Improvements
1. [file] — {issue description}

Classification:

  • 🔴 Fix Immediately: broken links, missing required fields, invalid enum values, failed idea without failure_reason, invalid JSON in edges, confidence out of range
  • 🟡 Recommended Fixes: xref asymmetry, dangling graph edges, broken claim references, unknown edge types
  • 🔵 Optional Improvements: orphan pages, quality suggestions, empty sections

Append log:

python3 tools/research_wiki.py log wiki/ "check | report: N 🔴, M 🟡, K 🔵"

Constraints

  • Report-only by default: without --fix, only reports, no modifications
  • --fix only repairs deterministic issues: xref reverse-link completion, missing fields filled with safe default values. Non-deterministic issues output recommendations (--suggest) for user approval
  • raw/ is read-only: do not modify files under raw/
  • graph/ is read-only: lint does not modify graph files, checks consistency only
  • LLM judgments labeled by source: automated checks and LLM judgments are clearly distinguished in the report
  • Idempotent: running multiple times produces the same result (unless wiki content changes)

Error Handling

  • wiki/ does not exist: report error and suggest running /init
  • graph files do not exist: skip the missing graph-file checks, note in report
  • Partial directory missing: skip checks for missing directories, list missing directories in report

Dependencies

Tools(via Bash)

  • python3 tools/lint.py --wiki-dir wiki/ [--json] [--fix] [--dry-run] [--suggest] — automated structural check + fix (core dependency)
  • python3 tools/research_wiki.py log wiki/ "<message>" — append log
  • python3 tools/research_wiki.py stats wiki/ — get statistics (optional, for the report)
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall