Skill Market

lsp

Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

GitHub
githubcommunitycodexmcp
0.0
0 installs69.2K GitHub starsby code-yeongyu

Skill Introduction

Overview
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

Core value

Turns reusable Debugging know-how into an installable skill, helping users complete github, community, codex, mcp work faster.

Target users

  • Developers, testers, and maintainers who handle Debugging tasks in Focus Code.
  • Teams that already trust workflows or content from code-yeongyu.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, codex, mcp that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Debugging, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, codex, mcp, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install lsp-39a814
View source

Detail Preview

SKILL.md

Primary filemarkdown2 KB

name: lsp description: Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

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. Prefer severity: "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.

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet