# Llvm Tooling

> Build Clang plugins, LibTooling tools, LLDB extensions, or clangd/LSP integrations. Use for developer tooling around LLVM, not compiler pipeline implementation.

- Skill: `neversight/llvm-tooling-2` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add neversight/llvm-tooling-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/neversight/llvm-tooling-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: neversight (https://skillmd.com/u/neversight)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/neversight/llvm-tooling-2

---


# LLVM tooling

Choose the LLVM interface that matches the user's integration surface and deployment model.

## Topic routing

- [Clang tools](references/clang-tools.md) for plugins, AST matchers, and standalone LibTooling applications.
- [Debugger and language server](references/debugger-and-language-server.md) for LLDB and clangd/LSP extensions.
- [Transformation and ecosystem](references/transformation-and-ecosystem.md) for source rewriting, refactoring, and comparable projects.
- [Resources](references/resources.md) for upstream references.

Preserve source locations, diagnostics, and compilation database behavior when they are part of the tool's contract. Use `compiler-development` when changing compilation semantics rather than building an external developer tool.