static-analysis
Uses LLVM infrastructure to perform deep static analysis for vulnerability detection and code verification.
Install
mkdir -p .claude/skills/static-analysis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3551" && unzip -o skill.zip -d .claude/skills/static-analysis && rm skill.zipInstalls to .claude/skills/static-analysis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Expertise in LLVM-based static analysis including dataflow analysis, pointer analysis, taint tracking, and program verification. Use this skill when implementing security scanners, bug finders, code quality tools, or performing program analysis research.Key capabilities
- →Perform dataflow analysis on LLVM IR
- →Construct dominator and post-dominator trees
- →Analyze pointer aliasing and points-to sets
- →Implement taint tracking for security analysis
- →Build data dependency graphs
How it works
The skill utilizes the LLVM analysis infrastructure to inspect program structure, data flow, and control flow through custom passes and built-in managers.
Inputs & outputs
When to use static-analysis
- →Building a security vulnerability scanner
- →Tracking variable definitions via dataflow analysis
- →Detecting control flow dominance relationships
- →Analyzing pointer aliasing in C++ code
About this skill
Static Analysis Skill
This skill covers static program analysis techniques using LLVM infrastructure for security research, vulnerability detection, and code quality assessment.
Analysis Categories
Dataflow Analysis
- Forward Analysis: Track values from definitions to uses
- Backward Analysis: Track from uses back to definitions
- May/Must Analysis: Conservative vs precise approximations
Control Flow Analysis
- Dominator Trees: Identify code dominance relationships
- Post-Dominator Trees: Control dependence analysis
- Loop Analysis: Detect and characterize loops
Pointer Analysis
- Flow-Insensitive: Andersen's, Steensgaard's algorithms
- Flow-Sensitive: Track pointer values at each program point
- Context-Sensitive: Distinguish calling contexts
LLVM Analysis Infrastructure
Using Built-in Analyses
#include "llvm/Analysis/AliasAnalysis.h"
#include "llvm/Analysis/LoopInfo.h"
#include "llvm/Analysis/DominatorTree.h"
void analyze(llvm::Function& F, llvm::FunctionAnalysisManager& FAM) {
// Get dominator tree
auto& DT = FAM.getResult<llvm::DominatorTreeAnalysis>(F);
// Get loop info
auto& LI = FAM.getResult<llvm::LoopAnalysis>(F);
// Get alias analysis
auto& AA = FAM.getResult<llvm::AAManager>(F);
// Check if two pointers may alias
llvm::AliasResult AR = AA.alias(Ptr1, Ptr2);
}
Implementing Custom Analysis
class TaintAnalysis {
std::set<llvm::Value*> taintedValues;
public:
void markTainted(llvm::Value* V) {
taintedValues.insert(V);
}
bool isTainted(llvm::Value* V) {
return taintedValues.count(V) > 0;
}
void propagate(llvm::Instruction* I) {
// Propagate taint through operations
for (auto& Op : I->operands()) {
if (isTainted(Op)) {
markTainted(I);
break;
}
}
}
};
Taint Analysis
Source-Sink Model
// Define taint sources (user input, network, files)
bool isTaintSource(llvm::CallInst* CI) {
llvm::Function* F = CI->getCalledFunction();
if (!F) return false;
static const std::set<std::string> sources = {
"read", "recv", "fread", "getenv", "gets", "scanf"
};
return sources.count(F->getName().str()) > 0;
}
// Define sensitive sinks (SQL queries, system calls, format strings)
bool isSensitiveSink(llvm::CallInst* CI) {
llvm::Function* F = CI->getCalledFunction();
if (!F) return false;
static const std::set<std::string> sinks = {
"system", "exec", "printf", "strcpy", "memcpy", "sql_query"
};
return sinks.count(F->getName().str()) > 0;
}
Interprocedural Analysis
- Track taint across function boundaries
- Handle indirect calls via call graph analysis
- Context-sensitivity for precision
Pointer Analysis Frameworks
Using Andersen's Analysis
#include "llvm/Analysis/CFLAndersAliasAnalysis.h"
// Check may-alias relationship
void checkAlias(llvm::AAResults& AA, llvm::Value* P1, llvm::Value* P2) {
switch (AA.alias(P1, P2)) {
case llvm::AliasResult::NoAlias:
// Definitely don't alias
break;
case llvm::AliasResult::MayAlias:
// Might alias
break;
case llvm::AliasResult::MustAlias:
// Always alias
break;
}
}
Points-To Sets
// Track what each pointer may point to
class PointsToAnalysis {
std::map<llvm::Value*, std::set<llvm::Value*>> pointsTo;
public:
void addPointsTo(llvm::Value* ptr, llvm::Value* target) {
pointsTo[ptr].insert(target);
}
const std::set<llvm::Value*>& getPointsTo(llvm::Value* ptr) {
return pointsTo[ptr];
}
};
Dependency Analysis
Data Dependency Graph (DDG)
#include "llvm/Analysis/DDG.h"
void buildDDG(llvm::Function& F, llvm::FunctionAnalysisManager& FAM) {
auto& LI = FAM.getResult<llvm::LoopAnalysis>(F);
for (auto* L : LI) {
llvm::DataDependenceGraph DDG(*L, FAM.getResult<llvm::AAManager>(F));
for (auto& Node : DDG) {
// Analyze data dependencies in loop
}
}
}
Program Slicing
- Forward slicing: Find all statements affected by a variable
- Backward slicing: Find all statements affecting a variable
- Use for debugging, testing, and security analysis
Major Static Analysis Tools
Comprehensive Frameworks
- Phasar: Industrial-strength LLVM-based analysis framework
- SVF: Scalable pointer analysis and value-flow analysis
- Joern: Code analysis platform with graph queries
- CodeChecker: Clang-based static analysis integration
Specialized Tools
- clam: Abstract interpretation framework
- dg: Dependence graph construction
- Semgrep: Pattern-based multi-language analysis
Security Analysis Applications
Vulnerability Detection
// Buffer overflow detection
void checkBufferAccess(llvm::GetElementPtrInst* GEP) {
// Get array size if available
llvm::Type* SourceType = GEP->getSourceElementType();
if (auto* AT = llvm::dyn_cast<llvm::ArrayType>(SourceType)) {
uint64_t arraySize = AT->getNumElements();
// Check if index might exceed bounds
llvm::Value* Index = GEP->getOperand(2);
// Perform range analysis on index
}
}
Use-After-Free Detection
- Track allocation/deallocation points
- Build reaching definitions for pointers
- Flag uses after free calls
Information Flow
- Track sensitive data (passwords, keys, PII)
- Detect leaks to logs, network, or untrusted sinks
- Implement declassification rules
Best Practices
- Soundness vs Completeness: Understand trade-offs
- Scalability: Use summaries for large codebases
- Path Sensitivity: Balance precision and performance
- False Positive Management: Prioritize actionable findings
- Incremental Analysis: Cache results for faster re-analysis
Integration with IDEs
Clangd/LSP Integration
- Provide real-time analysis feedback
- Integrate with editor diagnostics
- Support quick-fix suggestions
CI/CD Integration
- Run analysis on pull requests
- Block merges on critical findings
- Track analysis trends over time
Resources
See Static Analysis and Clang Plugins sections in README.md for comprehensive tool listings and research references.
Getting Detailed Information
When you need detailed and up-to-date resource links, tool lists, or project references, fetch the latest data from:
https://raw.githubusercontent.com/gmh5225/awesome-llvm-security/refs/heads/main/README.md
This README contains comprehensive curated lists of:
- Static analysis frameworks (Static Analysis section)
- Pointer analysis and taint tracking tools
- Program verification and bug finding tools
- Clang-based code analysis plugins
When not to use it
- →High-level source code analysis without LLVM IR
- →Real-time runtime monitoring
Prerequisites
Limitations
- →Requires LLVM IR as input
- →Trade-off between analysis precision and scalability
How it compares
It enables precise, compiler-level program analysis compared to pattern-based or regex-based code scanners.
Compared to similar skills
static-analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| static-analysis (this skill) | 5 | 6mo | No flags | Advanced |
| memory-safety-patterns | 4 | 4mo | No flags | Advanced |
| rr-debugger | 1 | 3mo | Review | Advanced |
| c-pro | 1 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by gmh5225
View all by gmh5225 →You might also like
memory-safety-patterns
sickn33
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
rr-debugger
gadievron
Deterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.
c-pro
sickn33
Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.
quality-checker
rdkcentral
Run comprehensive quality checks (static analysis, memory safety, thread safety, build verification) on the MemCapture codebase. Use when validating code changes or debugging before committing.
systemc-tools
intel
Use when writing, editing, reviewing, or debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library. Covers rules for module hierarchy, channels and ports, process declarations, reset behavior, sensitivity lists, SystemC and C++ data types and collections. Applie
gdb-cli
Anhvu1107
ALWAYS use this when the request matches GDB CLI: GDB debugging assistant for AI agents - analyze core dumps, debug live processes, investigate crashes and deadlocks with source code correlation