oh-my-opencode 4.9.2 → 4.11.0

package/dist/skills/lcx-doctor/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: lcx-doctor
+description: "Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install audited and compared with the latest LazyCodex and Codex code."
+metadata:
+  short-description: Diagnose LazyCodex/Codex install health against latest sources
+---
+
+# lcx-doctor
+
+You are a LazyCodex install doctor. Inspect the local installation, compare it against the latest LazyCodex and Codex sources, and return a PASS/WARN/FAIL report where every verdict cites the command output or file that produced it. Diagnose only: the only writes you make are under `/tmp`. Never mutate the user's install, config, or repositories during diagnosis; propose remediations and apply one only when the user explicitly asks afterward.
+
+Use GPT-5.5 style: outcome first, concise, evidence-bound.
+
+## Required Workflow
+
+1. Materialize the latest sources under `/tmp` first. Every source comparison below reads from these checkouts, never from memory. Re-sync on every run so a cached checkout cannot go stale:
+
+```bash
+sync_latest_source() {
+  REPO="$1"; DEST="$2"
+  if [ ! -d "$DEST/.git" ]; then
+    gh repo clone "$REPO" "$DEST" -- --depth=1 \
+      || git clone --depth=1 "https://github.com/$REPO" "$DEST"
+  fi
+  DEFAULT_BRANCH="$(git -C "$DEST" remote show origin | sed -n '/HEAD branch/s/.*: //p')"
+  git -C "$DEST" fetch --depth=1 origin "$DEFAULT_BRANCH"
+  git -C "$DEST" checkout -B "$DEFAULT_BRANCH" FETCH_HEAD
+}
+sync_latest_source code-yeongyu/lazycodex /tmp/lazycodex-source
+sync_latest_source openai/codex /tmp/openai-codex-source
+```
+
+2. Inventory the installed surface. Resolve `CODEX_HOME` (default `~/.codex`), then collect:
+   - `codex --version` and how `codex` resolves (`command -v codex`).
+   - Installed LazyCodex version: the `version` in the installed plugin manifest, discoverable with `find "${CODEX_HOME:-$HOME/.codex}/plugins" -path '*/.codex-plugin/plugin.json'`. Installed plugins live under `$CODEX_HOME/plugins/cache/<marketplace>/<name>/<version>/`.
+   - Latest LazyCodex version from `/tmp/lazycodex-source` (release tags or the version stamped in the repo) and latest Codex release (`gh release view --repo openai/codex`).
+   - OS, install method, and `lazycodex` / `lazycodex-ai` bin links resolving (`command -v`).
+3. Check config and wiring against the latest installer, not against assumptions. Read what the current installer under `/tmp/lazycodex-source` writes (installer sources live in the omo-codex package, e.g. `scripts/install/`), then verify the local equivalents:
+   - `$CODEX_HOME/config.toml` exists and parses; LazyCodex-managed entries match what the latest installer would write.
+   - Plugin payload present and non-empty: `hooks/hooks.json`, `skills/`, `.mcp.json`, components under the installed plugin root.
+   - Stale project-local leftovers the installer now removes (e.g. `.codex/hooks.json`, `.codex/skills` in the project) are flagged, not deleted.
+4. Probe the real surface. Run the built-in diagnostics first: `lazycodex doctor --json` (add `--verbose` when a check needs deeper traces) and fold its results into the report. A missing or crashing `lazycodex doctor` is itself a FAIL finding, not a reason to skip probing — fall back to `codex --version` plus a trivial non-interactive invocation that loads the plugin. Capture stderr verbatim; a clean exit with warnings is WARN, not PASS.
+5. Compare for drift. Where installed bundled files differ from the same files at the installed version, or the latest source renamed or removed something the local config still references, record it with both paths.
+6. Check whether each FAIL is already known: `gh issue list --repo code-yeongyu/lazycodex --search "<short symptom>" --state open` (and `openai/codex` when the failure points upstream). Link matches in the report instead of re-diagnosing from scratch.
+7. If a probe fails and the cause is not explained by config or source comparison, invoke `$omo:debugging` for the investigation. If Codex exposes only unqualified skill names in the current session, invoke `$debugging` and state that it is the OMO debugging skill.
+8. Emit the report.
+
+## Doctor Report Template
+
+```markdown
+## LazyCodex Doctor Report
+
+### Summary
+[One sentence: healthy, degraded, or broken — and the single most important next action.]
+
+### Environment
+- LazyCodex installed / latest:
+- Codex CLI installed / latest:
+- CODEX_HOME:
+- OS / install method:
+
+### Checks
+| Check | Verdict | Evidence |
+| --- | --- | --- |
+| Versions current | PASS/WARN/FAIL | [command output or file:line] |
+| config.toml integrity | PASS/WARN/FAIL | [evidence] |
+| Plugin payload wiring | PASS/WARN/FAIL | [evidence] |
+| Bin links / aliases | PASS/WARN/FAIL | [evidence] |
+| Runtime probe | PASS/WARN/FAIL | [evidence] |
+| Drift vs latest source | PASS/WARN/FAIL | [evidence, citing /tmp/lazycodex-source or /tmp/openai-codex-source paths] |
+
+### Remediations
+1. [Most important fix first: exact command or config edit, and what it resolves.]
+
+### Known Issues Matched
+- [issue URL — or "none found"]
+```
+
+## Follow-up Routing
+
+- Local misconfiguration or stale install: give the remediation; reinstalling via the standard LazyCodex install command is the default fix for payload drift.
+- Defect in LazyCodex or Codex product code: recommend `$lcx-report-bug` to file it, or `$lcx-contribute-bug-fix` when the user wants a fix PR. Both reuse the `/tmp` checkouts you already synced.
+
+## Stop Conditions
+
+Ask one narrow question only when a finding requires a destructive decision, such as deleting user-edited config or downgrading a version.
+
+Do not:
+
+- mutate config, installs, or repositories during diagnosis
+- report a verdict without captured evidence
+- compare against remembered source layout instead of `/tmp/lazycodex-source` and `/tmp/openai-codex-source`
+- declare healthy while any probe output was never captured

package/dist/skills/lcx-doctor/agents/openai.yaml

@@ -0,0 +1,11 @@
+interface:
+  display_name: "lcx-doctor (omo)"
+  short_description: "Diagnose LazyCodex/Codex install health against latest sources"
+  search_terms:
+    - "lcx-doctor"
+    - "lazycodex doctor"
+    - "lazycodex health check"
+    - "codex doctor"
+    - "lazycodex install broken"
+    - "omo-codex diagnose"
+  default_prompt: "Use $lcx-doctor to sync the latest LazyCodex and Codex sources into /tmp, inventory the local installation, compare versions, config, and wiring against the latest sources, probe the real surface, and report PASS/WARN/FAIL findings with evidence and remediations."

package/dist/skills/lcx-report-bug/SKILL.md

@@ -0,0 +1,237 @@
+---
+name: lcx-report-bug
+description: "Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing."
+metadata:
+  short-description: Route LazyCodex or Codex bugs with source evidence
+---
+
+# lcx-report-bug
+
+You are a LazyCodex bug router and reporter. Produce one useful GitHub issue or PR in English, backed by runtime evidence and source evidence rather than guesses. Route it to the repository that owns the defect:
+
+- `code-yeongyu/lazycodex` for LazyCodex, lazycodex-ai, omo-codex, marketplace, bundled skill, hook, MCP, installer, or packaging bugs. The artifact for this repo is always an issue — never a PR, because its contents are regenerated from the source tree on every release, so PRs there cannot be merged.
+- `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior. This is the only repo where this skill may create a PR.
+
+Use GPT-5.5 style: outcome first, concise, evidence-bound. Keep the workflow moving, but do not file an issue until the root cause and reproduction path are concrete enough for a maintainer to act.
+
+## Goal
+
+Create or prepare a GitHub issue or PR that includes:
+
+- clear title
+- target repository decision
+- environment
+- reproducible steps
+- expected behavior
+- actual behavior
+- confirmed or strongly evidenced root cause
+- fix approach, including files or components likely involved
+- verification plan
+- `lazycodex-generated` label and footer tag
+
+## Required Workflow
+
+1. Read the user's bug report and identify the affected surface: LazyCodex installer, Codex plugin, skill, hook, MCP, CLI alias, GitHub marketplace sync, or web/docs.
+2. Invoke `$omo:debugging` for the investigation. If Codex exposes only unqualified skill names in the current session, invoke `$debugging` and state that it is the OMO debugging skill.
+3. Materialize the latest LazyCodex and upstream Codex sources under `/tmp` before deciding ownership. Re-sync on every run so a cached checkout cannot go stale — stale source produces wrong routing and dead line references:
+
+```bash
+sync_latest_source() {
+  REPO="$1"; DEST="$2"
+  if [ ! -d "$DEST/.git" ]; then
+    gh repo clone "$REPO" "$DEST" -- --depth=1 \
+      || git clone --depth=1 "https://github.com/$REPO" "$DEST"
+  fi
+  DEFAULT_BRANCH="$(git -C "$DEST" remote show origin | sed -n '/HEAD branch/s/.*: //p')"
+  git -C "$DEST" fetch --depth=1 origin "$DEFAULT_BRANCH"
+  git -C "$DEST" checkout -B "$DEFAULT_BRANCH" FETCH_HEAD
+}
+sync_latest_source code-yeongyu/lazycodex /tmp/lazycodex-source
+sync_latest_source openai/codex /tmp/openai-codex-source
+```
+4. Follow the debugging skill far enough to gather runtime evidence:
+   - form at least three plausible hypotheses
+   - run the smallest reproduction that exercises the real surface
+   - confirm the root cause by observing the failing state
+   - identify the minimal fix path or maintainer action
+5. Compare runtime evidence with both `/tmp/lazycodex-source` and `/tmp/openai-codex-source` before choosing the target repo. Cite exact files, commands, logs, or source paths that support the routing decision.
+6. Choose the target repo:
+   - Use `code-yeongyu/lazycodex` when the bug is in LazyCodex integration, distribution, bundled plugin code, skills, hooks, MCP wiring, installer behavior, aliases, marketplace sync, docs, or any behavior that disappears in clean upstream Codex.
+   - Use `openai/codex` when the bug reproduces in clean upstream Codex without LazyCodex, or the failing behavior comes from Codex CLI core, plugin API contracts, sandboxing, approvals, config loading, or built-in tool behavior.
+   - If ownership remains ambiguous after evidence gathering, do not guess. Prepare the issue body with the uncertainty and ask one narrow routing question.
+7. Search for an existing issue in the selected repo before creating a new one. Search the other repo too when the ownership boundary is close:
+
+```bash
+TARGET_REPO="code-yeongyu/lazycodex" # or openai/codex
+gh issue list --repo "$TARGET_REPO" --search "<short error or symptom>" --state open
+```
+
+8. If a matching open issue exists, add a comment with the new evidence instead of creating a duplicate.
+9. Ensure the generated label exists in repositories you control:
+
+```bash
+LABEL_ARGS=()
+if gh label create lazycodex-generated --repo "$TARGET_REPO" --color "7C3AED" --description "Created by LazyCodex" --force; then
+  LABEL_ARGS=(--label lazycodex-generated)
+else
+  echo "Label management unavailable for $TARGET_REPO; keeping the footer tag only."
+fi
+```
+
+If the selected repo is `openai/codex` and label management is not available, still include the footer tag in the body and continue without claiming label creation succeeded.
+10. If no matching issue exists, create the issue with `gh` and apply the `lazycodex-generated` label.
+11. Create a PR only when the target repo is `openai/codex` AND the user asked for a PR, the fix is already implemented on a branch, or the smallest correct fix can be safely made there. Never create a PR or push a branch against `code-yeongyu/lazycodex` — always file an issue there, embedding the verified patch in the Proposed Fix section when one exists. Apply the `lazycodex-generated` label to every PR created by this skill. Otherwise create an issue with fix guidance.
+
+## Required Label And Footer
+
+Every issue body, evidence comment, and PR body created by this skill must use the GitHub label `lazycodex-generated` when the artifact supports labels. It must also end with this footer. Do not put content after it.
+
+```markdown
+---
+This issue or PR was generated by LazyCodex.
+Tag: lazycodex-generated
+```
+
+## Issue Body Template
+
+Write the issue body in English and keep it direct:
+
+```markdown
+## Summary
+[One or two sentences describing the user-visible failure.]
+
+## Environment
+- LazyCodex version:
+- Codex version:
+- OS:
+- Install method:
+- Relevant config:
+
+## Repository Decision
+- Target repository:
+- Why this belongs there:
+- LazyCodex evidence (runtime + `/tmp/lazycodex-source`):
+- Upstream Codex source evidence from `/tmp/openai-codex-source`:
+
+## Reproduction
+1. [Exact command or UI action]
+2. [Exact next step]
+3. [Observed failure trigger]
+
+## Expected Behavior
+[What should have happened.]
+
+## Actual Behavior
+[What happened instead, including exact error text or output.]
+
+## Evidence
+[Commands, logs, screenshots, traces, or links used to confirm the failure.]
+
+## Root Cause
+[Confirmed cause. If not fully confirmed, say what evidence supports it and what remains uncertain.]
+
+## Proposed Fix
+[Concrete implementation or operational fix. Include likely files, components, or commands.]
+
+## Verification Plan
+- [Check that reproduces the original failure]
+- [Check that proves the fix]
+- [Regression check for adjacent LazyCodex/Codex plugin behavior]
+
+---
+This issue or PR was generated by LazyCodex.
+Tag: lazycodex-generated
+```
+
+## PR Body Template
+
+Use this only when a PR is the right artifact, which is only ever for `openai/codex`:
+
+```markdown
+## Summary
+[One or two sentences describing the fix and the user-visible failure it resolves.]
+
+## Repository Decision
+- Target repository:
+- Why this belongs there:
+- LazyCodex evidence (runtime + `/tmp/lazycodex-source`):
+- Upstream Codex source evidence from `/tmp/openai-codex-source`:
+
+## Root Cause
+[Confirmed cause. Cite runtime evidence and source paths.]
+
+## Fix
+[What changed and why.]
+
+## Verification
+- [Check that reproduced the original failure before the fix]
+- [Check that passes after the fix]
+- [Regression check for adjacent behavior]
+
+---
+This issue or PR was generated by LazyCodex.
+Tag: lazycodex-generated
+```
+
+## GitHub Creation Path
+
+Prefer `gh`:
+
+```bash
+ISSUE_BODY="/tmp/lcx-report-bug-$(date +%Y%m%d-%H%M%S).md"
+$EDITOR "$ISSUE_BODY"
+gh issue create --repo "$TARGET_REPO" --title "<clear title>" "${LABEL_ARGS[@]}" --body-file "$ISSUE_BODY"
+```
+
+If `$EDITOR` is not usable, write the file with the available file-editing tool, then run the same `gh issue create` command.
+
+For an existing issue:
+
+```bash
+COMMENT_BODY="/tmp/lcx-report-bug-comment-$(date +%Y%m%d-%H%M%S).md"
+gh issue comment "<issue-number>" --repo "$TARGET_REPO" --body-file "$COMMENT_BODY"
+if [ "${#LABEL_ARGS[@]}" -gt 0 ]; then
+  gh issue edit "<issue-number>" --repo "$TARGET_REPO" --add-label lazycodex-generated
+fi
+```
+
+For a PR from a branch pushed to a fork — `openai/codex` only, never `code-yeongyu/lazycodex`:
+
+```bash
+PR_BODY="/tmp/lcx-report-bug-pr-$(date +%Y%m%d-%H%M%S).md"
+gh pr create --repo openai/codex --title "<clear title>" "${LABEL_ARGS[@]}" --body-file "$PR_BODY"
+```
+
+After creating or commenting, return the issue or PR URL and a short summary of the evidence used.
+
+## Browser use fallback
+
+If `gh` is unavailable, unauthenticated, or blocked, use Browser Use against the real GitHub page:
+
+1. Open the new issue page for the selected repo: `https://github.com/code-yeongyu/lazycodex/issues/new` or `https://github.com/openai/codex/issues/new`.
+2. Fill the title and body from the template.
+3. Submit the issue only after visually confirming the repo, title, and body.
+4. Capture the resulting issue URL.
+
+## Computer use fallback
+
+If Browser Use is unavailable but a desktop browser is open and authenticated, use Computer Use:
+
+1. Navigate to the new issue page for the selected repo: `https://github.com/code-yeongyu/lazycodex/issues/new` or `https://github.com/openai/codex/issues/new`.
+2. Fill the title and body.
+3. Verify the target repository and final text before submission.
+4. Submit and capture the issue URL.
+
+## Stop Conditions
+
+Stop and ask one narrow question only when the missing fact changes the issue materially, such as the affected version, a private log the agent cannot access, or whether the user wants a duplicate filed despite an existing matching issue.
+
+Do not file:
+
+- a PR or pushed branch targeting `code-yeongyu/lazycodex` — file the issue instead, always
+- a vague issue without reproduction steps
+- an issue that claims a root cause not supported by runtime evidence
+- a duplicate when commenting on an existing issue is enough
+- an issue without checking the latest `/tmp/lazycodex-source` and `/tmp/openai-codex-source` checkouts
+- a LazyCodex issue when the bug is proven to reproduce in clean upstream Codex
+- a fix PR without a concrete branch, implemented fix, and verification result

package/dist/skills/lcx-report-bug/agents/openai.yaml

@@ -0,0 +1,11 @@
+interface:
+  display_name: "lcx-report-bug (omo)"
+  short_description: "Route LazyCodex or Codex bugs with source evidence"
+  search_terms:
+    - "lcx-report-bug"
+    - "lazycodex bug"
+    - "lazycodex issue"
+    - "omo-codex bug"
+    - "openai codex bug"
+    - "codex upstream issue"
+  default_prompt: "Use $lcx-report-bug to investigate this LazyCodex or Codex bug, compare LazyCodex evidence with /tmp openai/codex source, choose the correct GitHub repo, and file an issue (or, for openai/codex only, a PR — never a PR on code-yeongyu/lazycodex) with reproduction, root cause, fix guidance, and the lazycodex-generated label and footer."

package/dist/skills/lsp-setup/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: lsp-setup
+description: "Configure a Language Server (LSP) for a specific language so editor/agent tooling — diagnostics, go-to-definition, find-references, rename — works. Use when you need to: configure LSP, lsp setup, set up or install a language server, fix 'no LSP server configured' / 'server not installed', choose between servers (basedpyright vs pyright vs ty vs ruff), or wire .codex/lsp-client.json / .opencode/lsp.json. 언어서버 설정. Routes by file extension to references/<language>/README.md for the exact builtin server, per-OS install commands (macOS/Linux/Windows), config snippets for both config files, initialization options, alternatives, and troubleshooting. Ships scripts: detect-lsp.ts (scan a project for languages + each server's install/config status) and verify-lsp.ts (run a real diagnostics roundtrip). Covers typescript, python, go, rust, c/c++, java, kotlin, c#/razor, swift, ruby, php, dart, elixir, zig, lua, bash, yaml, terraform, haskell, julia."
+---
+
+# LSP Setup
+
+Configure the right Language Server for a project so the `lsp` MCP tools
+(`diagnostics`, `goto_definition`, `find_references`, `symbols`, `rename`)
+actually work. This skill is an index: detect what a project needs, install the
+server, write the config, then verify with a real roundtrip.
+
+The list of servers we ship as **builtin** is the source of truth in
+`packages/lsp-tools-mcp/src/lsp/server-definitions.ts` (`BUILTIN_SERVERS` +
+`LSP_INSTALL_HINTS`). The per-language references below mirror it.
+
+---
+
+## PHASE 0 — LANGUAGE GATE (run first)
+
+Identify the language from the file extension, then **read the matching
+reference before installing or configuring anything**.
+
+| Extension(s) | Reference |
+|---|---|
+| `.ts .tsx .js .jsx .mjs .cjs .mts .cts .vue .svelte .astro` | `references/typescript/README.md` |
+| `.py .pyi` | `references/python/README.md` |
+| `.go` | `references/go/README.md` |
+| `.rs` | `references/rust/README.md` |
+| `.c .cpp .cc .cxx .h .hpp .hh .hxx` | `references/c-cpp/README.md` |
+| `.java` | `references/java/README.md` |
+| `.kt .kts` | `references/kotlin/README.md` |
+| `.cs .razor .cshtml` | `references/csharp/README.md` |
+| `.swift` | `references/swift/README.md` |
+| `.rb .rake .gemspec .ru` | `references/ruby/README.md` |
+| `.php` | `references/php/README.md` |
+| `.dart` | `references/dart/README.md` |
+| `.ex .exs` | `references/elixir/README.md` |
+| `.zig .zon` | `references/zig/README.md` |
+| `.lua` | `references/lua/README.md` |
+| `.sh .bash .zsh .ksh` | `references/bash/README.md` |
+| `.yaml .yml` | `references/yaml/README.md` |
+| `.tf .tfvars` | `references/terraform/README.md` |
+| `.hs .lhs` | `references/haskell/README.md` |
+| `.jl` | `references/julia/README.md` |
+
+---
+
+## WORKFLOW — detect → install → configure → verify
+
+### 1. Detect
+
+Scan the project to see which languages are present and whether each server is
+installed and configured:
+
+```bash
+bun scripts/detect-lsp.ts <projectDir>      # human report (default: cwd)
+bun scripts/detect-lsp.ts <projectDir> --json
+```
+
+For each detected language it prints the builtin server id, the executable it
+needs on `PATH`, whether that executable is installed, an install hint, and
+whether a project config file already references it.
+
+### 2. Install
+
+Open `references/<language>/README.md` and run the install command for your OS.
+Then confirm the executable resolves:
+
+```bash
+command -v <server-executable>   # e.g. typescript-language-server, gopls, rust-analyzer
+```
+
+### 3. Configure
+
+Most builtin servers need **no config** — they are resolved automatically by
+file extension. Write config only to: pick between competing servers, set a
+`priority`, pass `initialization` options, override `extensions`, set `env`, or
+`disable` a server.
+
+Two project-scoped config files, **identical JSON shape**:
+
+- Codex harness → `.codex/lsp-client.json` (user: `~/.codex/lsp-client.json`)
+- OpenCode/omo harness → `.opencode/lsp.json` (also `.omo/lsp.json`)
+
+```jsonc
+{
+  "lsp": {
+    "<server-id>": {
+      "command": ["<bin>", "<args>"],   // optional for builtin ids (supplied automatically)
+      "extensions": [".ext"],            // optional override
+      "priority": 100,                    // higher wins when several servers match an extension
+      "initialization": { },              // server-specific initializationOptions
+      "env": { "KEY": "value" },          // optional
+      "disabled": false                   // set true to turn a server off
+    }
+  }
+}
+```
+
+Rules enforced by `config-loader.ts`:
+
+- In a **project** config (`.codex/lsp-client.json`, `.opencode/lsp.json`) an
+  entry whose id is a **builtin** server inherits `command` automatically — you
+  only override `extensions` / `priority` / `initialization`. A non-builtin id
+  in a project config is **ignored**.
+- To define a **fully custom** (non-builtin) server with its own `command`, put
+  it in the **user** config (`~/.codex/lsp-client.json`, or the path set by
+  `LSP_TOOLS_MCP_USER_CONFIG`), where `command` + `extensions` are honored.
+- Project entries win over user entries; both win over builtin defaults.
+
+Each language reference gives a ready-to-paste snippet.
+
+### 4. Verify
+
+Run a real diagnostics roundtrip against a source file. This spawns the server,
+opens the file, requests diagnostics, and reports `OK`/`FAIL`:
+
+```bash
+bun scripts/verify-lsp.ts <path/to/file.ext>
+bun scripts/verify-lsp.ts <file> --timeout=90000
+```
+
+`OK` = the server started and answered. `FAIL: language server not installed`
+= go back to step 2. Other `FAIL` text carries the server/startup error.
+`SKIP` = the engine source could not be located; run from inside the omo
+repo/worktree, or call the `lsp` MCP `diagnostics` tool directly.
+
+---
+
+## Scripts
+
+| Script | Purpose |
+|---|---|
+| `scripts/detect-lsp.ts` | Scan a directory; per detected language report server id, install status, install hint, config status. `--json` for machine output. |
+| `scripts/verify-lsp.ts` | Real LSP diagnostics roundtrip for one file via the `lsp-tools-mcp` engine; `OK`/`FAIL`/`SKIP` + exit code 0/1/3. |
+| `scripts/lsp-server-table.ts` | Embedded snapshot of the primary builtin server per language (mirrors `server-definitions.ts`). |
+
+Run with [Bun](https://bun.sh): `curl -fsSL https://bun.sh/install | bash`.

package/dist/skills/lsp-setup/references/bash/README.md

@@ -0,0 +1,60 @@
+# Bash — LSP setup
+
+- **Builtin server:** `bash` — `bash-language-server start`
+- **Extensions:** `.sh .bash .zsh .ksh`
+- **Install hint:** `npm install -g bash-language-server`
+
+An alias id `bash-ls` exists with the identical command; either id works.
+
+## Install
+
+- **macOS:** `npm install -g bash-language-server`
+- **Linux:** `npm install -g bash-language-server`
+- **Windows:** `npm install -g bash-language-server` (PowerShell)
+
+For real diagnostics, also install `shellcheck`:
+
+- **macOS:** `brew install shellcheck`
+- **Linux:** `apt install shellcheck` (or `dnf install ShellCheck`)
+- **Windows:** `scoop install shellcheck`
+
+Confirm it resolves:
+
+```bash
+command -v bash-language-server
+command -v shellcheck
+```
+
+## Configure
+
+Builtin — usually NO config needed (auto-resolved by extension). Configure only to set priority, init options, override extensions, or disable. Same JSON shape in `.codex/lsp-client.json` (Codex) AND `.opencode/lsp.json` (OpenCode/omo):
+
+```json
+{ "lsp": { "bash": { "priority": 100 } } }
+```
+
+For builtin ids in a PROJECT config, `command` is supplied automatically — only set `priority`/`initialization`/`extensions`/`disabled`/`env`. A fully custom (non-builtin) server with its own `command` must go in the USER config (`~/.codex/lsp-client.json`).
+
+### Initialization options (only if commonly needed)
+
+None commonly required. `bash-language-server` discovers `shellcheck` on PATH automatically. To point at a non-PATH binary, export `SHELLCHECK_PATH` via `env`:
+
+```json
+{ "lsp": { "bash": { "env": { "SHELLCHECK_PATH": "/opt/bin/shellcheck" } } } }
+```
+
+## Alternatives
+
+- `shellcheck` standalone as a linter-only flow (no LSP).
+- `shfmt` for formatting (complements, does not replace, the LSP).
+
+## Troubleshooting
+- **PATH:** `bash-language-server` on PATH; reopen shell after `npm -g` install.
+- **No diagnostics:** `shellcheck` missing — diagnostics are powered by it; install and reopen.
+- **Wrong shell dialect:** `.zsh`/`.ksh` are linted as bash; shellcheck may flag shell-specific syntax.
+
+## Verify
+
+```bash
+bun ../../scripts/verify-lsp.ts path/to/file.sh
+```

package/dist/skills/lsp-setup/references/c-cpp/README.md

@@ -0,0 +1,61 @@
+# C / C++ — LSP setup
+
+- **Builtin server:** `clangd` — `clangd --background-index --clang-tidy`
+- **Extensions:** `.c .cpp .cc .cxx .c++ .h .hpp .hh .hxx .h++`
+- **Install hint:** `https://clangd.llvm.org/installation`
+
+## Install
+
+- **macOS:** `brew install llvm` (clangd ships in the LLVM keg; add its `bin` to PATH)
+- **Linux:** `apt install clangd` (Debian/Ubuntu); use your distro package elsewhere
+- **Windows:** install LLVM from `https://releases.llvm.org` or `winget install LLVM.LLVM`
+
+See `https://clangd.llvm.org/installation` for other platforms.
+
+Confirm it resolves:
+
+```bash
+command -v clangd
+```
+
+## Configure
+
+Builtin — usually NO config needed (auto-resolved by extension). Configure only to set priority, init options, override extensions, or disable. Same JSON shape in `.codex/lsp-client.json` (Codex) AND `.opencode/lsp.json` (OpenCode/omo):
+
+```json
+{ "lsp": { "clangd": { "priority": 100 } } }
+```
+
+For builtin ids in a PROJECT config, `command` is supplied automatically — only set `priority`/`initialization`/`extensions`/`disabled`/`env`. A fully custom (non-builtin) server with its own `command` must go in the USER config (`~/.codex/lsp-client.json`).
+
+### Initialization options (only if commonly needed)
+
+None commonly required. clangd reads flags from a project `.clangd` file rather
+than initializationOptions. The builtin command already passes
+`--background-index --clang-tidy`.
+
+## Compile commands
+
+clangd needs a `compile_commands.json` at the project root (or in `build/`) for
+accurate diagnostics and cross-file navigation. Generate it with:
+
+- **CMake:** `cmake -B build -DCMAKE_EXPORT_COMPILE_COMMANDS=ON` (symlink/copy `build/compile_commands.json` to the root)
+- **Make / other:** `bear -- make`
+
+Without it, clangd falls back to heuristic flags and reports spurious errors.
+
+## Alternatives
+
+None builtin. `ccls` exists as a third-party server but is not builtin — it would
+need a custom `command` in the USER config.
+
+## Troubleshooting
+- **PATH:** `clangd` must be on PATH; reopen shell after install. Homebrew LLVM is keg-only — add `$(brew --prefix llvm)/bin` to PATH.
+- **Spurious "file not found" / unknown flags:** missing or stale `compile_commands.json` — regenerate it after changing the build.
+- **Header-only diagnostics wrong:** ensure the header's translation unit appears in the compile database, or add a `.clangd` `CompileFlags` block.
+
+## Verify
+
+```bash
+bun ../../scripts/verify-lsp.ts path/to/file.cpp
+```