From lazycortex-wiki
Audit a wiki scope's integrity: orphan topics, broken See-also links and repo keys, index desync, missing summaries, stale glosses, unknown axes, duplicate branches, broken code <wiki> blocks, and scope overlaps. Read-only by default; applies fixable repairs only after the operator confirms.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lazycortex-wiki:lazy-wiki.doctorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the integrity audit over one wiki scope (or every configured scope), present the findings grouped by severity, and — only after the operator confirms — apply the fixable repairs. Fixable repairs are: rebuild the topic index (orphan-topic, index-desync), drop broken See-also lines (broken-see-also), and refresh stale glosses (stale-gloss). All other findings are report-only.
Run the integrity audit over one wiki scope (or every configured scope), present the findings grouped by severity, and — only after the operator confirms — apply the fixable repairs. Fixable repairs are: rebuild the topic index (orphan-topic, index-desync), drop broken See-also lines (broken-see-also), and refresh stale glosses (stale-gloss). All other findings are report-only.
Invocation: /wiki.doctor [<scope-id>]
Prerequisites: /wiki.install has run and at least one scope is configured in .claude/lazy.settings.json[wiki.scopes].
This skill has 4 ordered steps. The executing agent MUST NOT skip, merge, reorder, or silently omit any step. To make dropped steps structurally impossible:
TaskCreate with exactly one task per step below — no merging, no abbreviation, no renaming. The canonical list (use these titles verbatim):
Phase 1 — Run the auditPhase 2 — Present findingsPhase 3 — Confirm and apply fixesLog the runin_progress on enter and completed on exit. "Completed" means the step's logic ran AND an outcome word was produced. No-ops must emit an explicit outcome (asserted, unchanged, skipped-per-user-choice, …).TaskList shows every prior task completed or explicitly skipped with an outcome.Run the read-only audit first — never pass --apply in this phase.
Bash(lazycortex-wiki doctor <scope-id>) when the operator named a scope, or Bash(lazycortex-wiki doctor) to audit every configured scope.
The command prints findings grouped per scope and severity (FAIL / WARN / INFO), tags each fixable finding (fixable), and ends with a grand-total count. It exits 0 when the audit ran; a non-zero exit means the named scope id is unknown or no scopes are configured — surface that message to the operator and stop (do not proceed to later phases).
Outcome: audited.
Summarise the captured output for the operator: the per-scope counts by severity, and a short list of the concrete findings (check name, node path, message). Call out which findings are fixable (orphan-topic, index-desync, broken-see-also, stale-gloss) versus report-only (broken-repo-key, missing-summary, unknown-axis, dup-branch, broken-wiki-block, scope-overlap).
If the audit found zero findings, report "scope clean" and skip to the Log step (mark Phase 3 skipped with outcome skipped-per-user-choice).
Outcome: presented.
If there are no fixable findings, skip with outcome skipped-per-user-choice.
Otherwise ask the operator via AskUserQuestion whether to apply the fixable repairs. State exactly what --apply will do: rebuild the topic index, drop the broken See-also lines, and refresh stale glosses — these write tracked files. Offer at minimum: apply fixes, leave read-only.
skipped-per-user-choice. Do not run --apply.Bash(lazycortex-wiki doctor <scope-id> --apply) (same scope argument as Phase 1, add --apply). The command reports each fix as (fixed). Report what was applied. Outcome applied.Outcome: applied or skipped-per-user-choice.
Write a run log to ./.logs/claude/lazy-wiki.doctor/ per lazy-log.logging.
Bash(mkdir -p ./.logs/claude/lazy-wiki.doctor)git_sha via Bash(git rev-parse HEAD) and git_branch via Bash(git rev-parse --abbrev-ref HEAD); use no-git if either fails.Bash(date -u +%Y-%m-%d_%H-%M-%S) → timestamp for the filename.Write the log to ./.logs/claude/lazy-wiki.doctor/<timestamp>.md with frontmatter:---
git_sha: <sha>
git_branch: <branch>
date: <YYYY-MM-DD HH:MM:SS UTC>
input: "<scope-id or 'all scopes'>"
---
# lazy-wiki.doctor
## Actions
- <bullet per step with outcome>
## Result
<success/failure + one-sentence summary of finding counts and any fixes applied>
Outcome: logged.
One line per task in the canonical list, with its outcome word. A missing line is a bug.
/wiki.doctor reports "unknown scope ''" — the scope id is not in lazy.settings.json[wiki.scopes] → run /wiki.configure to create it, or re-invoke with a known id./wiki.doctor reports "no wiki scopes configured" — no scopes exist yet → run /wiki.install then /wiki.configure first.Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub mebius-san/lazy-cortex --plugin lazycortex-wiki