codeql

Scans codebases for security vulnerabilities using CodeQL data flow and taint tracking analysis.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/curtismu7/AI-DEMO2 --skill codeql-curtismu7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codeql
Source: https://github.com/curtismu7/AI-DEMO2/tree/main/security/codeql
Command: npx skills add https://github.com/curtismu7/AI-DEMO2 --skill codeql-curtismu7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finding deep security vulnerabilities like SQL injection, command injection, and path traversal requires interprocedural data flow analysis that simple pattern matching cannot provide. This Skill automates the full CodeQL pipeline — building a database, modeling project-specific APIs with data extensions, and running filtered security queries — so you get trustworthy SARIF results instead of silent zero-finding runs. ## Core Features & Use Cases - Database Building with Quality Gates: Creates CodeQL databases for Python, JavaScript/TypeScript, Go, Java/Kotlin, C/C++, C#, Ruby, and Swift, with sequential build methods, macOS Apple Silicon workarounds, and quality assessment (baseline LoC, extractor errors). - Data Extension Generation: Detects custom wrappers around database calls, request parsing, and shell execution that CodeQL does not model, then generates source/sink/summary YAML models and validates them with before-and-after analysis. - Two Scan Modes: Run-all mode (security-and-quality plus security-experimental suites) and important-only mode (high-precision findings with post-analysis severity filtering), both using explicit .qls suite files to avoid silent query dropping. - Use Case: Point it at a repository and say "run a full CodeQL scan" — it discovers or builds the database, creates data extensions for unmodeled APIs, executes the analysis, and delivers filtered SARIF results in a single output directory. ## Quick Start Ask the assistant to run a CodeQL security scan on this repository and report the high-confidence vulnerabilities.

Frequently Asked Questions about codeql

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

FAQPage Schema
How do I scan a codebase for vulnerabilities with CodeQL?▼

Build a CodeQL database from the source tree, optionally generate data extensions for custom APIs, then run codeql database analyze with an explicit .qls suite file. Results are written as SARIF, which can be filtered by precision and security severity.

What languages does CodeQL support for security scanning?▼

CodeQL supports Python, JavaScript/TypeScript, Go, Java/Kotlin, C/C++, C#, Ruby, and Swift. Interpreted languages need no build step, while compiled languages require build tracing so the extractor can observe compilation.

Why does my CodeQL analysis return zero findings?▼

Zero findings usually indicate poor database quality, missing source/sink models, or silent suite filtering from a pack's defaultSuiteFile. Check baseline lines of code, extractor error counts, and always use an explicit .qls suite instead of passing pack names directly.

How do I fix CodeQL build failures on macOS Apple Silicon?▼

Exit code 137 on Apple Silicon is an arm64e/arm64 mismatch between system tools and CodeQL's libtrace.dylib, not a real build failure. Use a Homebrew arm64 compiler with multi-step tracing, or run the build under Rosetta x86_64 emulation.

When should I use Semgrep instead of CodeQL?▼

Use Semgrep for quick pattern searches, single-file checks, or when you cannot build a compiled-language project. CodeQL is better for deep interprocedural taint tracking and comprehensive multi-pack security audits.