@codyswann/lisa 2.121.0 → 2.122.0

package/plugins/lisa-typescript/{.codex-plugin → hooks}/hooks.json

@@ -6,7 +6,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "./hooks/block-suppress-directives.sh"
+            "command": "${PLUGIN_ROOT}/hooks/block-suppress-directives.sh"
           }
         ]
       }
@@ -17,15 +17,15 @@
         "hooks": [
           {
             "type": "command",
-            "command": "./hooks/format-on-edit.sh"
+            "command": "${PLUGIN_ROOT}/hooks/format-on-edit.sh"
           },
           {
             "type": "command",
-            "command": "./hooks/sg-scan-on-edit.sh"
+            "command": "${PLUGIN_ROOT}/hooks/sg-scan-on-edit.sh"
           },
           {
             "type": "command",
-            "command": "./hooks/lint-on-edit.sh"
+            "command": "${PLUGIN_ROOT}/hooks/lint-on-edit.sh"
           }
         ]
       }

package/plugins/lisa-typescript-agy/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "lisa-typescript",
+  "version": "2.122.0",
+  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
+  "author": {
+    "name": "Cody Swann"
+  },
+  "dependencies": [
+    "lisa"
+  ]
+}

package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json

@@ -0,0 +1,43 @@
+{
+  "name": "lisa-typescript",
+  "version": "2.122.0",
+  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
+  "author": {
+    "name": "Cody Swann"
+  },
+  "dependencies": [
+    "lisa"
+  ],
+  "hooks": {
+    "preToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/block-suppress-directives.sh"
+          }
+        ]
+      }
+    ],
+    "postToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/format-on-edit.sh"
+          },
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/sg-scan-on-edit.sh"
+          },
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/lint-on-edit.sh"
+          }
+        ]
+      }
+    ]
+  }
+}

package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json

@@ -0,0 +1,43 @@
+{
+  "name": "lisa-typescript",
+  "version": "2.122.0",
+  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
+  "author": {
+    "name": "Cody Swann"
+  },
+  "dependencies": [
+    "lisa"
+  ],
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/block-suppress-directives.sh"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/format-on-edit.sh"
+          },
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/sg-scan-on-edit.sh"
+          },
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/lint-on-edit.sh"
+          }
+        ]
+      }
+    ]
+  }
+}

package/plugins/lisa-typescript-cursor/hooks/block-suppress-directives.sh

@@ -0,0 +1,73 @@
+#!/bin/bash
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+#
+# PreToolUse hook (Write|Edit): block adding error-suppression directives to
+# JS/TS source. Suppressing the type checker, linter, or formatter hides real
+# defects instead of fixing them, so it is a documented last resort (see the
+# base "ASK FIRST" governance rule). The agent should stop and get the user's
+# approval rather than slip a suppression past silently.
+#
+# Inspects only the NEW text the tool introduces, scoped to JS/TS files, and
+# matches the directive only in comment syntax (// or /*) so prose, strings,
+# and identifiers that merely mention these tokens are not flagged.
+# Exit code 2 blocks the tool call and surfaces stderr to Claude.
+# Reference: https://docs.claude.com/en/docs/claude-code/hooks
+
+JSON_INPUT=$(cat)
+
+# Project rule (.claude/rules/PROJECT_RULES.md): never parse JSON in shell with
+# grep/sed/cut/awk — always use jq. Fail open without jq so we never hard-block
+# the agent on missing tooling.
+command -v jq >/dev/null 2>&1 || exit 0
+
+FILE_PATH=$(printf '%s' "$JSON_INPUT" | jq -r '.tool_input.file_path // empty')
+[ -n "$FILE_PATH" ] || exit 0
+
+# Only guard JS/TS source. Directives in other file types (docs, configs that
+# document the rules, this script) are not suppressions.
+case "${FILE_PATH##*.}" in
+  ts | tsx | js | jsx | mjs | cjs) ;;
+  *) exit 0 ;;
+esac
+
+# Resolve the new text per tool shape:
+#   Write     -> tool_input.content
+#   MultiEdit -> tool_input.edits[].new_string
+#   Edit      -> tool_input.new_string
+NEW_TEXT=$(printf '%s' "$JSON_INPUT" | jq -r '
+  .tool_input as $i
+  | if   ($i.content     // null) != null then $i.content
+    elif ($i.edits       // null) != null then ([$i.edits[].new_string] | join("\n"))
+    elif ($i.new_string  // null) != null then $i.new_string
+    else "" end')
+
+# Comment-syntax-only match: a // or /* opener, optional whitespace, then the
+# suppression directive. @ts-expect-error is intentionally NOT matched — it is
+# the safer alternative this hook steers toward.
+DIRECTIVE_RE='(//|/\*)[[:space:]]*(@ts-(ignore|nocheck)|eslint-disable|biome-ignore|prettier-ignore)'
+
+if printf '%s' "$NEW_TEXT" | grep -Eq "$DIRECTIVE_RE"; then
+  cat >&2 <<MSG
+❌ Blocked: error-suppression directive in $FILE_PATH
+
+You are adding a @ts-ignore / @ts-nocheck / eslint-disable / biome-ignore /
+prettier-ignore comment. These silence the type checker, linter, or formatter
+instead of fixing the underlying problem. They are a last resort, not a default.
+
+Fix it properly first:
+  - Resolve the actual type/lint error rather than suppressing it.
+  - Add the missing annotation, narrow the type, or restructure the code so the
+    rule passes legitimately.
+  - For a faulty dependency type, prefer a typed wrapper or module augmentation.
+
+If — and only if — there is genuinely no other way (e.g. a known upstream bug):
+  - STOP and get the user's approval before suppressing (base "ASK FIRST" rule).
+  - Prefer @ts-expect-error over @ts-ignore (it fails once the error is gone).
+  - Scope the disable to one line and one rule, never a whole file.
+  - Include a "-- <reason>" description (eslint-comments/require-description).
+MSG
+  exit 2
+fi
+
+exit 0

package/plugins/lisa-typescript-cursor/hooks/format-on-edit.sh

@@ -0,0 +1,79 @@
+#!/bin/bash
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+
+# Hook script to format files with Prettier after Claude edits them
+# This script receives JSON input via stdin with tool information
+# Reference: https://docs.claude.com/en/docs/claude-code/hooks
+
+# Read the JSON input from stdin
+JSON_INPUT=$(cat)
+
+# Extract the file path from the tool_input. Use jq for robust JSON parsing
+# (never grep/sed/cut — a JSON shape change silently skips formatting). Fail
+# open without jq so we never hard-block an edit.
+command -v jq >/dev/null 2>&1 || exit 0
+FILE_PATH=$(printf '%s' "$JSON_INPUT" | jq -r '.tool_input.file_path // empty')
+
+# Check if we successfully extracted a file path
+if [ -z "$FILE_PATH" ]; then
+    echo "⚠ Skipping Prettier: Could not extract file path from Edit tool input" >&2
+    exit 0  # Exit gracefully to not interrupt Claude's workflow
+fi
+
+# Check if the file exists
+if [ ! -f "$FILE_PATH" ]; then
+    echo "⚠ Skipping Prettier: File does not exist: $FILE_PATH" >&2
+    exit 0  # Exit gracefully
+fi
+
+# Get the file extension
+FILE_EXT="${FILE_PATH##*.}"
+
+# Check if this is a TypeScript or JavaScript file that should be formatted
+# Based on package.json format command: "prettier --write \"src/**/*.ts\" \"test/**/*.ts\""
+case "$FILE_EXT" in
+    ts|tsx|js|jsx|json)
+        # File type is supported for formatting
+        ;;
+    *)
+        echo "ℹ Skipping Prettier: File type .$FILE_EXT is not configured for auto-formatting"
+        exit 0
+        ;;
+esac
+
+# Change to the project directory to ensure package manager commands work
+cd "$CLAUDE_PROJECT_DIR" || exit 0
+
+# Resolve Prettier binary — prefer local node_modules/.bin, then package-manager exec
+if [ -x "./node_modules/.bin/prettier" ]; then
+    PRETTIER_CMD="./node_modules/.bin/prettier"
+    PKG_MANAGER="npm"
+elif [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
+    PRETTIER_CMD="bunx prettier"
+    PKG_MANAGER="bun"
+elif [ -f "pnpm-lock.yaml" ]; then
+    PRETTIER_CMD="pnpm exec prettier"
+    PKG_MANAGER="pnpm"
+elif [ -f "yarn.lock" ]; then
+    PRETTIER_CMD="yarn exec prettier"
+    PKG_MANAGER="yarn"
+else
+    PRETTIER_CMD="npx prettier"
+    PKG_MANAGER="npm"
+fi
+
+# Run Prettier on the specific file
+echo "🎨 Running Prettier on: $FILE_PATH"
+$PRETTIER_CMD --write "$FILE_PATH" 2>&1 | grep -v "run v" | grep -v "Done in"
+
+# Check the exit status
+if [ ${PIPESTATUS[0]} -eq 0 ]; then
+    echo "✓ Successfully formatted: $(basename "$FILE_PATH")"
+else
+    echo "⚠ Prettier formatting failed for: $FILE_PATH" >&2
+    echo "  You may need to run '$PKG_MANAGER run format' manually to fix formatting issues." >&2
+fi
+
+# Always exit successfully to not interrupt Claude's workflow
+exit 0

package/plugins/lisa-typescript-cursor/hooks/lint-on-edit.sh

@@ -0,0 +1,134 @@
+#!/bin/bash
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+# =============================================================================
+# Lint-on-Edit Hook (PostToolUse - Write|Edit)
+# =============================================================================
+# Runs oxlint --fix, then ESLint --fix --quiet --cache on each edited
+# TypeScript file. Part of the inline self-correction pipeline:
+#   prettier → ast-grep → oxlint --fix → eslint --fix
+#
+# oxlint runs first because it's a Rust-native linter (~1000x faster) that
+# covers the majority of rules, leaving only the slow / type-aware / plugin
+# rules for ESLint to handle.
+#
+# Behavior:
+#   - Exit 0: lint passes or auto-fix resolved all errors
+#   - Exit 2: unfixable errors remain — blocks Claude so it fixes them immediately
+#
+# @see .claude/rules/verfication.md "Self-Correction Loop" section
+# =============================================================================
+
+# Extract file path from JSON input. Use jq for robust JSON parsing (never
+# grep/sed/cut — a shape change would silently skip the blocking lint gate).
+# Fail open without jq so we never hard-block an edit.
+command -v jq >/dev/null 2>&1 || exit 0
+FILE_PATH=$(cat | jq -r '.tool_input.file_path // empty')
+
+if [ -z "$FILE_PATH" ] || [ ! -f "$FILE_PATH" ]; then
+    exit 0
+fi
+
+# Check if file type is supported (TypeScript only)
+case "${FILE_PATH##*.}" in
+    ts|tsx) ;;
+    *) exit 0 ;;
+esac
+
+# Validate project directory
+if [ -z "${CLAUDE_PROJECT_DIR:-}" ]; then
+    exit 0
+fi
+
+# Check if file is in a source directory
+RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}"
+case "$RELATIVE_PATH" in
+    src/*|apps/*|libs/*|test/*|tests/*|features/*|components/*|hooks/*|screens/*|app/*|constants/*|utils/*|providers/*|stores/*) ;;
+    *) exit 0 ;;
+esac
+
+cd "$CLAUDE_PROJECT_DIR" || exit 0
+
+# Resolve oxlint and ESLint binaries — prefer local node_modules/.bin
+if [ -x "./node_modules/.bin/oxlint" ]; then
+    OXLINT_CMD="./node_modules/.bin/oxlint"
+elif [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
+    OXLINT_CMD="bunx oxlint"
+elif [ -f "pnpm-lock.yaml" ]; then
+    OXLINT_CMD="pnpm exec oxlint"
+elif [ -f "yarn.lock" ]; then
+    OXLINT_CMD="yarn exec oxlint"
+else
+    OXLINT_CMD="npx oxlint"
+fi
+
+if [ -x "./node_modules/.bin/eslint" ]; then
+    ESLINT_CMD="./node_modules/.bin/eslint"
+elif [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
+    ESLINT_CMD="bunx eslint"
+elif [ -f "pnpm-lock.yaml" ]; then
+    ESLINT_CMD="pnpm exec eslint"
+elif [ -f "yarn.lock" ]; then
+    ESLINT_CMD="yarn exec eslint"
+else
+    ESLINT_CMD="npx eslint"
+fi
+
+# 1) oxlint --fix (REQUIRED in the Phase 2 hybrid pipeline)
+# If oxlint is missing the project is out of sync with the current Lisa
+# governance — fail loudly rather than silently skipping. ESLint alone is
+# no longer a complete lint pass.
+if [ ! -x "./node_modules/.bin/oxlint" ] && ! command -v "${OXLINT_CMD%% *}" >/dev/null 2>&1; then
+    echo "oxlint is required but not installed in this project." >&2
+    echo "Add 'oxlint' as a devDependency (Lisa governance pins it via package.lisa.json) and run install." >&2
+    exit 2
+fi
+
+if [ ! -f ".oxlintrc.json" ] && [ ! -f ".oxlintrc.jsonc" ] && [ ! -f "oxlint.config.ts" ]; then
+    echo "oxlint is installed but no .oxlintrc.json found. Run 'lisa update' to install the stack template." >&2
+    exit 2
+fi
+
+echo "Running oxlint --fix on: $FILE_PATH"
+OX_OUTPUT=$($OXLINT_CMD --fix --quiet "$FILE_PATH" 2>&1)
+OX_EXIT=$?
+if [ $OX_EXIT -ne 0 ]; then
+    # Re-run without --fix to capture remaining errors
+    OX_OUTPUT=$($OXLINT_CMD --quiet "$FILE_PATH" 2>&1)
+    OX_EXIT=$?
+    if [ $OX_EXIT -ne 0 ]; then
+        echo "oxlint found unfixable errors in: $FILE_PATH" >&2
+        echo "$OX_OUTPUT" >&2
+        exit 2
+    fi
+fi
+
+# 2) ESLint --fix --quiet --cache
+# --quiet: suppress warnings, only show errors
+# --cache: use ESLint cache for performance
+# --rule: disable no-unused-vars auto-fix to prevent removing imports that Claude
+#         plans to use in a subsequent edit (pre-commit hook still catches them)
+echo "Running ESLint --fix on: $FILE_PATH"
+
+# First pass: attempt auto-fix
+OUTPUT=$($ESLINT_CMD --fix --quiet --cache --rule '@typescript-eslint/no-unused-vars: off' "$FILE_PATH" 2>&1)
+FIX_EXIT=$?
+
+if [ $FIX_EXIT -eq 0 ]; then
+    echo "ESLint: No errors in $(basename "$FILE_PATH")"
+    exit 0
+fi
+
+# Auto-fix resolved some issues but errors remain — re-run to get remaining errors
+OUTPUT=$($ESLINT_CMD --quiet --cache "$FILE_PATH" 2>&1)
+LINT_EXIT=$?
+
+if [ $LINT_EXIT -eq 0 ]; then
+    echo "ESLint: Auto-fixed all errors in $(basename "$FILE_PATH")"
+    exit 0
+fi
+
+# Unfixable errors remain — block with feedback
+echo "ESLint found unfixable errors in: $FILE_PATH" >&2
+echo "$OUTPUT" >&2
+exit 2

package/plugins/lisa-typescript-cursor/hooks/sg-scan-on-edit.sh

@@ -0,0 +1,71 @@
+#!/bin/bash
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+
+# Hook script to run ast-grep scan after Claude edits files
+# This script receives JSON input via stdin with tool information
+# Reference: https://docs.claude.com/en/docs/claude-code/hooks
+# Note: This hook is BLOCKING - it returns non-zero exit codes so Claude must fix issues
+
+# Extract file path from JSON input. Use jq for robust JSON parsing (never
+# grep/sed/cut — a shape change would turn this blocking scan into a silent
+# no-op). Fail open without jq so we never hard-block an edit.
+command -v jq >/dev/null 2>&1 || exit 0
+FILE_PATH=$(cat | jq -r '.tool_input.file_path // empty')
+
+if [ -z "$FILE_PATH" ] || [ ! -f "$FILE_PATH" ]; then
+    exit 0
+fi
+
+# Check if file type is supported (TypeScript, JavaScript)
+case "${FILE_PATH##*.}" in
+    ts|tsx|js|jsx|mjs|cjs) ;;
+    *) exit 0 ;;
+esac
+
+# Validate project directory
+if [ -z "${CLAUDE_PROJECT_DIR:-}" ]; then
+    exit 0
+fi
+
+# Check if file is in a source directory
+RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}"
+case "$RELATIVE_PATH" in
+    src/*|apps/*|libs/*|test/*|tests/*|features/*|components/*|hooks/*|screens/*|app/*|constants/*|utils/*|providers/*|stores/*) ;;
+    *) exit 0 ;;
+esac
+
+cd "$CLAUDE_PROJECT_DIR" || exit 0
+
+# Verify ast-grep configuration exists
+if [ ! -f "sgconfig.yml" ]; then
+    exit 0
+fi
+
+# Verify rules are defined
+RULE_COUNT=$(find ast-grep/rules -name "*.yml" -o -name "*.yaml" 2>/dev/null | grep -v ".gitkeep" | wc -l | tr -d ' ')
+if [ "$RULE_COUNT" -eq 0 ]; then
+    exit 0
+fi
+
+# Detect package manager
+if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
+    PKG_MANAGER="bun"
+elif [ -f "pnpm-lock.yaml" ]; then
+    PKG_MANAGER="pnpm"
+elif [ -f "yarn.lock" ]; then
+    PKG_MANAGER="yarn"
+else
+    PKG_MANAGER="npm"
+fi
+
+# Run ast-grep scan
+echo "Running ast-grep scan on: $FILE_PATH"
+if OUTPUT=$($PKG_MANAGER run sg:scan "$FILE_PATH" 2>&1); then
+    echo "ast-grep: No issues found in $(basename "$FILE_PATH")"
+    exit 0
+else
+    echo "ast-grep found issues in: $FILE_PATH" >&2
+    echo "$OUTPUT" >&2
+    exit 1
+fi

package/plugins/lisa-wiki/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.121.0",
+  "version": "2.122.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.121.0",
+  "version": "2.122.0",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-agy/ci/lisa-wiki-validate.yml

@@ -0,0 +1,33 @@
+# lisa-wiki validation — OPTIONAL. Installed into a project by `/setup --with-ci`.
+#
+# Runs the deterministic wiki validators on pull requests that touch the wiki.
+# Node-only, no extra dependencies (the validators are dependency-free).
+#
+# LISA_WIKI_SCRIPTS must point at the installed plugin's scripts/ directory.
+# `/setup --with-ci` wires this — either by resolving the installed plugin path or
+# by vendoring the plugin's scripts/ into the repo (default below: .lisa-wiki/scripts).
+name: 🧠 LLM Wiki Validate
+
+on:
+  pull_request:
+    paths:
+      - 'wiki/**'
+      - '.lisa-wiki/**'
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    env:
+      LISA_WIKI_SCRIPTS: ${{ vars.LISA_WIKI_SCRIPTS || '.lisa-wiki/scripts' }}
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-node@v6
+        with:
+          node-version: '22'
+          package-manager-cache: false
+
+      - name: Validate config
+        run: node "$LISA_WIKI_SCRIPTS/validate-config.mjs" wiki/lisa-wiki.config.json
+
+      - name: Lint wiki (strict — warnings block once the repo is at hard-enforcement)
+        run: node "$LISA_WIKI_SCRIPTS/lint-wiki.mjs" --wiki wiki --config wiki/lisa-wiki.config.json --strict

package/plugins/lisa-wiki-agy/commands/add-ingest.md

@@ -0,0 +1,6 @@
+---
+description: "Scaffold a project-specific front-door ingest skill that does something unique (classify a source, fetch from a special system, stamp domain frontmatter) and then chains into /ingest. Extends ingestion without forking the kernel."
+argument-hint: "<short name for the new ingest path>"
+---
+
+Use the lisa-wiki-add-ingest skill to generate a thin, registered front-door ingest skill: interview the project for the source type, bucket, frontmatter, and side-effect class; emit a lisa-wiki-local-<name> skill that enriches then chains into /ingest; and register it under customConnectors. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/add-role.md

@@ -0,0 +1,6 @@
+---
+description: "Scaffold a domain-expert digital-staff role over the wiki — a dual-runtime subagent (Claude + Codex) plus a staff doc page — from a config.staff[] entry. The plugin only sets the subagent up; running/scheduling it is out of scope."
+argument-hint: "<role name, e.g. Legal | Finance | Sales>"
+---
+
+Use the lisa-wiki-add-role skill to turn a role into a wiki/staff/<id>.md doc page and brain-pointed subagents on both runtimes (Claude .claude/agents/<id>.md + Codex .codex/agents/<id>.toml), pointed at the role's owned wiki domain. Setup-only — invocation/scheduling/routing is out of scope. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/doctor.md

@@ -0,0 +1,6 @@
+---
+description: "Verify that the wiki is correctly set up and (after migration) fully functional. Runs deterministic checks plus functional smoke tests, writes a doctor report, and returns an overall verdict (READY / READY_WITH_WARNINGS / NOT_READY). The final gate of /migrate; re-runnable anytime."
+argument-hint: "[--migration]"
+---
+
+Use the lisa-wiki-doctor skill to run the post-migration/post-setup verification checklist: structure & config, integrity & safety, no-loss/parity, runtime surfaces on both runtimes, functional smoke tests (no extra PR), mode-specific, and git/CI/distribution. Write wiki/state/migration/doctor-report.json and report the verdict + blocking items. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/ingest.md

@@ -0,0 +1,6 @@
+---
+description: "Ingest source material into the LLM Wiki. With an argument (URL, file path, or prompt) ingest that one source; with no argument run a full ingest across every enabled non-external-write source. Routes to the right connector and runs the ordered pipeline (source note → synthesis → index → log → verify → state → commit/PR)."
+argument-hint: "[url | file path | prompt]   (omit for a full ingest)"
+---
+
+Use the lisa-wiki-ingest skill to ingest into the wiki: route the input to the right connector (or, with no argument, run a full ingest across all enabled non-external-write sources), then run the ordered pipeline — sanitized source note, synthesis with citations, index, log, verification, and state advancement, then commit/PR per policy. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/lint.md

@@ -0,0 +1,6 @@
+---
+description: "Health-check the LLM Wiki: orphan pages, contradictions, stale claims, broken internal links, missing index/log coverage, structure violations, and secret/tenant leaks. Read-only — reports findings, does not fix them."
+argument-hint: ""
+---
+
+Use the lisa-wiki-lint skill to run the wiki's integrity checks and report findings by severity (PASS/WARN/FAIL). It diagnoses only — fixes go through /ingest, /setup, or /migrate. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/migrate.md

@@ -0,0 +1,6 @@
+---
+description: "Migrate an existing hand-rolled wiki onto the lisa-wiki kernel — phased and compatibility-first, with a strict no-loss guarantee (renaming is fine; losing functionality or data is not). Ends by running /doctor."
+argument-hint: "[--phase <0|1|1b|2|3|4|5>]"
+---
+
+Use the lisa-wiki-migrate skill to move this repo's bespoke wiki onto the kernel in reviewable phases: inventory, adopt kernel, absorb documentation, consolidate runtime + connectors, normalize by touch, then hard-enforce — parity-checking each migrated artifact before deleting the old one, and finishing with /doctor. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/onboard-me.md

@@ -0,0 +1,6 @@
+---
+description: "Onboard a user to the project via its LLM Wiki: interview them about themselves in relation to the project, then give a guided tour and sample questions. Read-mostly by default (session-local); --save-memory persists the capture to project-scoped memory only. No PRs, no PII written into the wiki, never global memory."
+argument-hint: "[--save-memory] [--write-audience-note]"
+---
+
+Use the lisa-wiki-onboard-me skill to onboard the user: briefly interview their role and goals (read-mostly, session-local by default; with --save-memory persist to project-scoped memory only — never global memory, never PII into the wiki), then summarize what the project is, show the folder map, and offer sample /query prompts tuned to their role. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/query.md

@@ -0,0 +1,6 @@
+---
+description: "Answer a question from the LLM Wiki with citations. Reads the index, drills into relevant pages, and synthesizes a cited answer. Read-only by default; files new synthesis back only when explicitly asked."
+argument-hint: "<question>"
+---
+
+Use the lisa-wiki-query skill to answer from the wiki with citations: locate relevant pages via the index, synthesize a cited answer, and say plainly when the wiki cannot support an answer. Read-only unless the user explicitly asks to persist new synthesis. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/setup/wiki.md

@@ -0,0 +1,6 @@
+---
+description: "Scaffold, repair, verify, or upgrade the project's LLM Wiki from its config. Alias for lisa-wiki setup in the Lisa setup command family."
+argument-hint: "[--upgrade] [--with-ci]"
+---
+
+Use the lisa-wiki-setup skill to bring the wiki into conformance from wiki/lisa-wiki.config.json: validate config, ask purpose + README mode, scaffold the canonical structure, render the contract snapshot (stamping kernelVersion), seed the staff roster, then verify with /doctor. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/setup-automations.md

@@ -0,0 +1,6 @@
+---
+description: "Set up the recurring LLM Wiki ingest automation on the local workstation using the runtime's native scheduler (Codex automations / Claude /schedule): wiki-ingest, a full /lisa-wiki:ingest cycle, once a day by default (override with cadence). A declarative spec — it states what to schedule and how often; the runtime's native automation mechanism does the creating. Named lisa-wiki-auto-<project>-* so it never collides with the base /lisa:setup-automations set. The wiki counterpart of /lisa:setup-automations, separate because the wiki plugin is standalone."
+argument-hint: "[cadence=daily|weekly|every-<n>-hours]"
+---
+
+Use the lisa-wiki-setup-automations skill to create the recurring wiki-ingest automation via this runtime's native scheduler (Codex automations / Claude /schedule), running a full /lisa-wiki:ingest cycle on the resolved cadence (default daily) and naming it lisa-wiki-auto-<project>-ingest so teardown stays precise. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/setup.md

@@ -0,0 +1,6 @@
+---
+description: "Scaffold, repair, verify, or upgrade the project's LLM Wiki from its config. Asks the wiki's purpose and README mode, renders the contract snapshot, scaffolds the canonical folders, and seeds the staff roster. Idempotent and non-destructive."
+argument-hint: "[--upgrade] [--with-ci]"
+---
+
+Use the lisa-wiki-setup skill to bring the wiki into conformance from wiki/lisa-wiki.config.json: validate config, ask purpose + README mode, scaffold the canonical structure, render the contract snapshot (stamping kernelVersion), seed the staff roster, then verify with /doctor. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/status.md

@@ -0,0 +1,6 @@
+---
+description: "Report Lisa wiki source freshness across enabled connectors. Read-only — summarizes last ingest evidence, skipped/blocker reasons, and targeted next actions without running ingestion."
+argument-hint: "[--json] [--wiki <path>] [--config <path>]"
+---
+
+Use the lisa-wiki-status skill to render the wiki source freshness report from `wiki/lisa-wiki.config.json`, `wiki/log.md`, `wiki/sources/**`, and `wiki/state/**`. This is read-only and must not ingest, edit, branch, commit, push, or open PRs. $ARGUMENTS

package/plugins/lisa-wiki-agy/commands/tear-down-automations.md

@@ -0,0 +1,6 @@
+---
+description: "Remove the recurring LLM Wiki ingest automation /lisa-wiki:setup-automations created for this project (the lisa-wiki-auto-<project>-* set) using the runtime's native scheduler (Codex automations / Claude /schedule). A declarative spec — it states which automation to remove; the runtime's native mechanism does the removing. Removes only this project's wiki automation, never the base set or other projects'."
+argument-hint: ""
+---
+
+Use the lisa-wiki-tear-down-automations skill to remove this project's lisa-wiki-auto-<project>-* automation via this runtime's native scheduler (Codex automations / Claude /schedule), leaving the base /lisa:setup-automations set, other projects', and non-Lisa automations untouched. $ARGUMENTS

package/plugins/lisa-wiki-agy/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "lisa-wiki",
+  "version": "2.122.0",
+  "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
+  "author": {
+    "name": "Cody Swann"
+  }
+}