llvm-tooling

Build LLVM/Clang developer tools for AST analysis and IDE integration.

69|11|Updated May 16, 2026
One-click install
npx skills add https://github.com/NeverSight/NeverC --skill llvm-tooling-neversight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llvm-tooling
Source: https://github.com/NeverSight/NeverC/tree/main/.agents/skills/llvm-tooling
Command: npx skills add https://github.com/NeverSight/NeverC --skill llvm-tooling-neversight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you design and implement developer tooling that performs accurate source-level analysis, debugging assistance, and IDE-ready language features using LLVM and Clang infrastructure.

Core Features & Use Cases

  • Clang plugin development: Extend Clang during compilation by traversing the AST and emitting diagnostics or transforming behavior.
  • LibTooling for standalone analyzers: Build command-line tools that run AST matchers over translation units and produce structured results.
  • LLDB extension development: Add custom LLDB commands and scripted processes to inspect state and streamline debugging workflows.
  • Clangd/LSP integration: Provide editor experiences via LSP features like code actions and custom configuration for consistent diagnostics.

Quick Start

Run an AST-matcher-based LibTooling analysis over a C/C++ file by compiling the tool against LLVM/Clang and executing it with the same include paths and compile flags as your project.

Frequently Asked Questions about llvm-tooling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a standalone C++ code analyzer using Clang LibTooling?

Build a standalone C++ code analyzer with Clang LibTooling by compiling a command-line tool against LLVM/Clang APIs, running AST matchers over translation units with matching compile flags to produce structured source analysis results.

Can I extend clangd LSP to provide custom code actions and diagnostics in my editor?

Extend clangd LSP to provide custom code actions and diagnostics by implementing language-server extension hooks, enabling consistent IDE-ready language features and custom configuration for editor integration.

What is the best way to develop a Clang plugin for AST traversal and custom diagnostics?

Develop a Clang plugin for AST traversal and custom diagnostics by extending Clang during compilation, implementing AST visitors and frontend actions to emit diagnostics or transform behavior directly within the compiler pipeline.

How do I add custom commands to LLDB for scripted debugging workflows?

Add custom commands to LLDB for scripted debugging workflows by implementing debugger extension hooks, allowing you to inspect program state and streamline debugging processes within the LLDB environment.

Do I need matching compile flags to run AST matchers over my project files?

You need matching compile flags and include paths to run AST matchers over your project files, ensuring the LibTooling analyzer processes translation units identically to your standard project compilation.

When should I use a Clang plugin versus a standalone LibTooling analyzer?

Use a Clang plugin when you need to extend compilation directly and emit in-pipeline diagnostics; use a standalone LibTooling analyzer when you need command-line tools that run AST matchers independently and output structured results.