codeql

Run CodeQL static analysis to detect security vulnerabilities and data-flow issues.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/mejango/juicy-vision --skill codeql-mejango
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codeql
Source: https://github.com/mejango/juicy-vision/tree/main/.claude/plugins/static-analysis/skills/codeql
Command: npx skills add https://github.com/mejango/juicy-vision --skill codeql-mejango

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeQL static analysis solves the problem of identifying security vulnerabilities and data-flow issues in codebases.

Core Features & Use Cases

  • Interprocedural data-flow tracking: Trace tainted data across function calls to sinks.
  • Language-agnostic security audits: Build CodeQL databases for multiple languages and run custom queries to detect vulnerabilities.
  • CI/CD integration: Integrate CodeQL into pipelines for automated analysis on commits and pull requests.

Quick Start

Install the CodeQL CLI, create a database for your language, and run analyses with your queries to produce a SARIF report.

Frequently Asked Questions about codeql

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

FAQPage Schema
How do I automate static analysis for security vulnerabilities in a CI/CD pipeline?▼

You can automate static analysis by integrating CodeQL into your CI/CD pipelines to automatically identify security vulnerabilities and data-flow issues on commits and pull requests.

How does interprocedural data-flow tracking identify security vulnerabilities?▼

Interprocedural data-flow tracking identifies security vulnerabilities by tracing tainted data across function calls to sinks, enabling the detection of complex data-flow issues within codebases.

Can I run custom queries to detect vulnerabilities across multiple programming languages?▼

Yes, you can build CodeQL databases for multiple languages and run custom queries to perform language-agnostic security audits, detecting vulnerabilities across various project sizes.

What is the best way to generate actionable security analysis reports for a codebase?▼

The best way to generate actionable security analysis reports is to install the CodeQL CLI, create a database for your language, and run analyses with your queries to produce a SARIF report.

Do I need to create a database before running CodeQL static analysis?▼

Yes, database creation is a required step before running analyses; you must create a CodeQL database for your specific language to query for security vulnerabilities and generate results.

Does CodeQL static analysis work for projects of any size?▼

CodeQL static analysis is applicable across languages and project sizes, enabling database creation, custom queries, and CI/CD security audits for diverse development workflows.