lsp
Lets your agent get diagnostic information and code definitions. It's used to check references, symbols, and rename safety in the project.
What it does
This tool helps you understand and manage 'language servers' that assist with programming. It can check for errors, find code definitions, search for where something is used, and even help rename parts of your code safely.
When to use it
- ✓When you want to know which programming tools are installed and working.
- ✓To find errors in a specific file after making changes.
- ✓To rename a variable or function throughout your project without breaking anything.
Example of what to ask your AI
“Check for errors in my 'main.py' file and tell me where the 'calculate_total' function is used across the project.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool communicates with 'language servers' that analyze your code. It uses specific commands to request information like errors, definitions, or references, and receives this information back to show you.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add code-yeongyu/oh-my-openagent --skill lspOr download just the file:
curl -L https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/packages/omo-codex/plugin/components/lsp/skills/lsp/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Codex LSP
Call lsp MCP tools through the tool interface; lsp.*/mcp__lsp__* are tool-call names, not shell commands.
Tools
lsp.status: list configured, installed, missing, disabled, and active language servers.lsp.diagnostics: check one file or directory for LSP diagnostics. Preferseverity: "error"after edits.lsp.goto_definition: locate a symbol definition from file, line, and character.lsp.find_references: find usages of a symbol across the workspace.lsp.symbols: inspect document symbols or search workspace symbols.lsp.prepare_rename: check whether a rename is valid at a position.lsp.rename: apply a language-server workspace edit for a rename.
Config
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.
FAQ
What are 'language servers'?
They are programs that help your code editor understand your code, providing features like error checking, autocompletion, and navigation.
Why would I use the `lsp.status` command first?
It shows which language servers are configured, installed, missing, or disabled. It's useful for knowing if a server needed for another function is absent.
What happens if I try to rename something and it goes wrong?
Before renaming, you can use `lsp.prepare_rename` to check if the rename is safe. The `lsp.rename` tool attempts to apply the rename safely across the project.
Details
Original description by the author
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
Popularity
- GitHub stars
- 70k
- Ranking position
- #1718
- License
- NOASSERTION
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
comment-checker
Helps your agent understand and respond to feedback from automatic comment checkers. It's useful when the agent needs to process information from tools that automatically review code or content.
code-yeongyu/oh-my-openagent
lcx-contribute-bug-fix
Helps your agent contribute bug fixes for LazyCodex-related projects. It creates issues or pull requests to ensure code quality.
code-yeongyu/oh-my-openagent
lcx-doctor
Lets your agent check the health of LazyCodex and Codex CLI installations. It's useful when the system behaves oddly after updates or changes.
code-yeongyu/oh-my-openagent
lcx-report-bug
Helps your agent report bugs in detail for LazyCodex projects. It creates issues with useful information for developers to fix the problem.
code-yeongyu/oh-my-openagent
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC