菜单
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'.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/rjroy/vibe-garden --skill lint命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| 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'. |
Health-check the wiki. Find what's broken, what's stale, what's drifted. Produce a report the maintainer can act on.
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.
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:
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.
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:
For each stale page:
fg-status field to stale. For Markdown pages, update frontmatter. For HTML pages, update or add the fg-status meta tag.After updating all stale pages, include the list of modified files in the report output under the stale sources section: Modified: [path list].
If a source file no longer exists, record it as a missing source (also a warning).
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.
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
[warning] Stale page
Page: .lore/reference/auth-decision.md
Newer sources: .lore/work/retros/auth-rollout.md
[warning] Missing source
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.
Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".
Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.
Use when the wiki has outgrown its flat layout and pages need grouping into category directories. Reorganizes .lore/reference/ into category and subcategory trees, rewrites the index, and repairs every referrer. Triggers include "stratify the wiki", "organize the reference directory", "group the wiki into categories", "the wiki is too flat", and "reorganize the field guide".