comment-checker
Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
Claude Code
$ npx -y skills add code-yeongyu/oh-my-openagent --skill lsp --agent claude-code
Codex
$ npx skills add code-yeongyu/oh-my-openagent --skill lsp -a codex -y
Cursor
$ npx skills add code-yeongyu/oh-my-openagent --skill lsp -a cursor -y
Gemini CLI
$ npx skills add code-yeongyu/oh-my-openagent --skill lsp -a gemini-cli -y
GitHub Copilot
$ npx skills add code-yeongyu/oh-my-openagent --skill lsp -a github-copilot -y
OpenCode
$ npx skills add code-yeongyu/oh-my-openagent --skill lsp -a opencode -y
Windsurf
$ npx skills add code-yeongyu/oh-my-openagent --skill lsp -a windsurf -y
name: lsp description: Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
Call `lsp` MCP tools through the tool interface; `lsp.*`/`mcp__lsp__*` are tool-call names, not shell commands.
Project config lives at `.codex/lsp-client.json`; user config lives at `~/.codex/lsp-client.json`.
{
"lsp": {
"typescript": {
"command": ["typescript-language-server", "--stdio"],
"extensions": [".ts", ".tsx", ".js", ".jsx"]
}
}
}Use `lsp.status` first when diagnostics report a missing language server.
Your tool for real work. But it's an agent. OmO is one omo command that turns your tokens into finished work: research across ten thousand sources, a deck people actually get, backends, frontends, code.
Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs.…
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or…
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…
Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or…
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.