Generated banner for Codeql
Generated logo for Codeql

Codeql

GitHubOfficialFirst committed by VeVarunSharmaDistributed by GitHub

  • Skill
  • Tool integration
  • Security
  • MIT
  • No issues found

From the author

Comprehensive guide for setting up and configuring CodeQL code scanning via GitHub Actions workflows and the CodeQL CLI. This skill should be used when users need help with code scanning configuration, CodeQL workflow files, CodeQL CLI commands, SARIF output, security analysis setup, or troubleshooting CodeQL analysis.
— the description by VeVarunSharma

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides procedural instructions for setting up CodeQL to perform automated code scanning. It covers both the GitHub Actions workflow integration for automated CI/CD pipelines and the standalone CodeQL CLI for local analysis. The documentation includes details on language support, build modes, query suite selection, SARIF output management, and troubleshooting common analysis issues.

What it does

  • Configures CodeQL code scanning within GitHub Actions workflows.
  • Provides commands for local database creation and analysis using the CodeQL CLI.
  • Explains how to manage and interpret SARIF output files.
  • Details how to configure language matrices, build modes, and custom query packs.
  • Offers guidance on alert triage, severity levels, and GitHub Copilot Autofix integration.
  • Provides troubleshooting steps for common analysis failures and environment requirements.

When to use it

  • When setting up automated security scanning in a GitHub repository.
  • When you need to run CodeQL analysis locally on a development machine.
  • When customizing CodeQL workflows for monorepos or specific build requirements.
  • When troubleshooting failed CodeQL analysis or build mode configurations.
  • When managing or dismissing security alerts generated by CodeQL.

Advantages

  • Supports a wide range of programming languages.
  • Integrates directly into GitHub Actions for automated security checks.
  • Allows for granular control over analysis via custom query packs and configuration files.
  • Provides clear paths for both default and advanced setup scenarios.
  • Facilitates local analysis and debugging through the CodeQL CLI.

Usage examples

“How do I set up a basic CodeQL workflow in GitHub Actions?”
The agent will provide a template for a .github/workflows/codeql.yml file, explaining the necessary steps for initialization, language matrix configuration, and analysis.
“How can I run CodeQL locally on my machine?”
The agent will guide you through downloading the CodeQL bundle, creating a database with the CLI, and running the analysis command to generate a SARIF file.
“What should I do if my CodeQL autobuild fails?”
The agent will suggest switching to manual build mode and provide instructions on how to insert custom build commands into your workflow.
“How do I interpret the severity of a CodeQL alert?”
The agent will explain the difference between standard severity and security severity, including how CVSS scores influence the reported alert level.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/codeql/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip codeql.zip -d .agents/skills

Documentation by VeVarunSharma

CodeQL Code Scanning

This skill provides procedural guidance for configuring and running CodeQL code scanning — both through GitHub Actions workflows and the standalone CodeQL CLI.

When to Use This Skill

Use this skill when the request involves:

  • Creating or customizing a codeql.yml GitHub Actions workflow

  • Choosing between default setup and advanced setup for code scanning

  • Configuring CodeQL language matrix, build modes, or query suites

  • Running CodeQL CLI locally (codeql database create, database analyze, github upload-results)

  • Understanding or interpreting SARIF output from CodeQL

  • Troubleshooting CodeQL analysis failures (build modes, compiled languages, runner requirements)

  • Setting up CodeQL for monorepos with per-component scanning

  • Configuring dependency caching, custom query packs, or model packs

Supported Languages

CodeQL supports the following language identifiers:

LanguageIdentifierAlternatives
C/C++c-cppc, cpp
C#csharp—
Gogo—
Java/Kotlinjava-kotlinjava, kotlin
JavaScript/TypeScriptjavascript-typescriptjavascript, typescript
Pythonpython—
Rubyruby—
Rustrust—
Swiftswift—
GitHub Actionsactions—

Alternative identifiers are equivalent to the standard identifier (e.g., javascript does not exclude TypeScript analysis).

Core Workflow — GitHub Actions

Step 1: Choose Setup Type
  • Default setup — Enable from repository Settings → Advanced Security → CodeQL analysis. Best for getting started quickly. Uses none build mode for most languages.

  • Advanced setup — Create a .github/workflows/codeql.yml file for full control over triggers, build modes, query suites, and matrix strategies.

To switch from default to advanced: disable default setup first, then commit the workflow file.

Step 2: Configure Workflow Triggers

Define when scanning runs:

on:
  push:
    branches: [main, protected]
  pull_request:
    branches: [main]
  schedule:
    - cron: '30 6 * * 1'  # Weekly Monday 6:30 UTC
  • push — scans on every push to specified branches; results appear in Security tab

  • pull_request — scans PR merge commits; results appear as PR check annotations

  • schedule — periodic scans of the default branch (cron must exist on default branch)

  • merge_group — add if repository uses merge queues

To skip scans for documentation-only PRs:

on:
  pull_request:
    paths-ignore:
      - '**/*.md'
      - '**/*.txt'

paths-ignore controls whether the workflow runs, not which files are analyzed.

Step 3: Configure Permissions

Set least-privilege permissions:

permissions:
  security-events: write   # Required to upload SARIF results
  contents: read            # Required to checkout code
  actions: read             # Required for private repos using codeql-action
Step 4: Configure Language Matrix

Use a matrix strategy to analyze each language in parallel:

jobs:
  analyze:
    name: Analyze (${{ matrix.language }})
    runs-on: ubuntu-latest
    strategy:
      fail-fast: false
      matrix:
        include:
          - language: javascript-typescript
            build-mode: none
          - language: python
            build-mode: none

For compiled languages, set the appropriate build-mode:

  • none — no build required (supported for C/C++, C#, Java, Rust)

  • autobuild — automatic build detection

  • manual — custom build commands (advanced setup only)

For detailed per-language autobuild behavior and runner requirements, search references/compiled-languages.md.

Step 5: Configure CodeQL Init and Analysis
steps:
  - name: Checkout repository
    uses: actions/checkout@v4

  - name: Initialize CodeQL
    uses: github/codeql-action/init@v4
    with:
      languages: ${{ matrix.language }}
      build-mode: ${{ matrix.build-mode }}
      queries: security-extended
      dependency-caching: true

  - name: Perform CodeQL Analysis
    uses: github/codeql-action/analyze@v4
    with:
      category: "/language:${{ matrix.language }}"

Query suite options:

  • security-extended — default security queries plus additional coverage

  • security-and-quality — security plus code quality queries

  • Custom query packs via packs: input (e.g., codeql/javascript-queries:AlertSuppression.ql)

Dependency caching: Set dependency-caching: true on the init action to cache restored dependencies across runs.

Analysis category: Use category to distinguish SARIF results in monorepos (e.g., per-language, per-component).

Step 6: Monorepo Configuration

For monorepos with multiple components, use the category parameter to separate SARIF results:

category: "/language:${{ matrix.language }}/component:frontend"

To restrict analysis to specific directories, use a CodeQL configuration file (.github/codeql/codeql-config.yml):

paths:
  - apps/
  - services/
paths-ignore:
  - node_modules/
  - '**/test/**'

Reference it in the workflow:

- uses: github/codeql-action/init@v4
  with:
    config-file: .github/codeql/codeql-config.yml
Step 7: Manual Build Steps (Compiled Languages)

If autobuild fails or custom build commands are needed:

- language: c-cpp
  build-mode: manual

Then add explicit build steps between init and analyze:

- if: matrix.build-mode == 'manual'
  name: Build
  run: |
    make bootstrap
    make release

Core Workflow — CodeQL CLI

Step 1: Install the CodeQL CLI

Download the CodeQL bundle (includes CLI + precompiled queries):

# Download from https://github.com/github/codeql-action/releases
# Extract and add to PATH
export PATH="$HOME/codeql:$PATH"

# Verify installation
codeql resolve packs
codeql resolve languages

Always use the CodeQL bundle, not a standalone CLI download. The bundle ensures query compatibility and provides precompiled queries for better performance.

Step 2: Create a CodeQL Database
# Single language
codeql database create codeql-db \
  --language=javascript-typescript \
  --source-root=src

# Multiple languages (cluster mode)
codeql database create codeql-dbs \
  --db-cluster \
  --language=java,python \
  --command=./build.sh \
  --source-root=src

For compiled languages, provide the build command via --command.

Step 3: Analyze the Database
codeql database analyze codeql-db \
  javascript-code-scanning.qls \
  --format=sarif-latest \
  --sarif-category=javascript \
  --output=results.sarif

Common query suites: <language>-code-scanning.qls, <language>-security-extended.qls, <language>-security-and-quality.qls.

Step 4: Upload Results to GitHub
codeql github upload-results \
  --repository=owner/repo \
  --ref=refs/heads/main \
  --commit=<commit-sha> \
  --sarif=results.sarif

Requires GITHUB_TOKEN environment variable with security-events: write permission.

CLI Server Mode

To avoid repeated JVM initialization when running multiple commands:

codeql execute cli-server

For detailed CLI command reference, search references/cli-commands.md.

Alert Management

Severity Levels

Alerts have two severity dimensions:

  • Standard severity: Error, Warning, Note

  • Security severity: Critical, High, Medium, Low (derived from CVSS scores; takes display precedence)

Copilot Autofix

GitHub Copilot Autofix generates fix suggestions for CodeQL alerts in pull requests automatically — no Copilot subscription required. Review suggestions carefully before committing.

Alert Triage in PRs
  • Alerts appear as check annotations on changed lines

  • Check fails by default for error/critical/high severity alerts

  • Configure merge protection rulesets to customize the threshold

  • Dismiss false positives with a documented reason for audit trail

For detailed alert management guidance, search references/alert-management.md.

Custom Queries and Packs

Using Custom Query Packs
- uses: github/codeql-action/init@v4
  with:
    packs: |
      my-org/[email protected]
      codeql/javascript-queries:AlertSuppression.ql
Creating Custom Query Packs

Use the CodeQL CLI to create and publish packs:

# Initialize a new pack
codeql pack init my-org/my-queries

# Install dependencies
codeql pack install

# Publish to GitHub Container Registry
codeql pack publish
CodeQL Configuration File

For advanced query and path configuration, create .github/codeql/codeql-config.yml:

paths:
  - apps/
  - services/
paths-ignore:
  - '**/test/**'
  - node_modules/
queries:
  - uses: security-extended
packs:
  javascript-typescript:
    - my-org/my-custom-queries

Code Scanning Logs

Summary Metrics

Workflow logs include key metrics:

  • Lines of code in codebase — baseline before extraction

  • Lines extracted — including external libraries and auto-generated files

  • Extraction errors/warnings — files that failed or produced warnings during extraction

Debug Logging

To enable detailed diagnostics:

  • GitHub Actions: re-run the workflow with "Enable debug logging" checked

  • CodeQL CLI: use --verbosity=progress++ and --logdir=codeql-logs

Troubleshooting

Common Issues
ProblemSolution
Workflow not triggeringVerify on: triggers match event; check paths/branches filters; ensure workflow exists on target branch
Resource not accessible errorAdd security-events: write and contents: read permissions
Autobuild failureSwitch to build-mode: manual and add explicit build commands
No source code seenVerify --source-root, build command, and language identifier
C# compiler failureCheck for /p:EmitCompilerGeneratedFiles=true conflicts with .sqlproj or legacy projects
Fewer lines scanned than expectedSwitch from none to autobuild/manual; verify build compiles all source
Kotlin in no-build modeDisable and re-enable default setup to switch to autobuild
Cache miss every runVerify dependency-caching: true on init action
Out of disk/memoryUse larger runners; reduce analysis scope via paths config; use build-mode: none
SARIF upload failsEnsure token has security-events: write; check 10 MB file size limit
SARIF results exceed limitsSplit across multiple uploads with different --sarif-category; reduce query scope
Two CodeQL workflowsDisable default setup if using advanced setup, or remove old workflow file
Slow analysisEnable dependency caching; use --threads=0; reduce query suite scope

For comprehensive troubleshooting with detailed solutions, search references/troubleshooting.md.

Hardware Requirements (Self-Hosted Runners)
Codebase SizeRAMCPU
Small (<100K LOC)8 GB+2 cores
Medium (100K–1M LOC)16 GB+4–8 cores
Large (>1M LOC)64 GB+8 cores

All sizes: SSD with ≥14 GB free disk space.

Action Versioning

Pin CodeQL actions to a specific major version:

uses: github/codeql-action/init@v4      # Recommended
uses: github/codeql-action/autobuild@v4
uses: github/codeql-action/analyze@v4

For maximum security, pin to a full commit SHA instead of a version tag.

Reference Files

For detailed documentation, load the following reference files as needed:

  • references/workflow-configuration.md — Full workflow trigger, runner, and configuration options

    • Search patterns: trigger, schedule, paths-ignore, db-location, model packs, alert severity, merge protection, concurrency, config file

  • references/cli-commands.md — Complete CodeQL CLI command reference

    • Search patterns: database create, database analyze, upload-results, resolve packs, cli-server, installation, CI integration

  • references/sarif-output.md — SARIF v2.1.0 object model, upload limits, and third-party support

    • Search patterns: sarifLog, result, location, region, codeFlow, fingerprint, suppression, upload limits, third-party, precision, security-severity

  • references/compiled-languages.md — Build modes and autobuild behavior per language

    • Search patterns: C/C++, C#, Java, Go, Rust, Swift, autobuild, build-mode, hardware, dependency caching

  • references/troubleshooting.md — Comprehensive error diagnosis and resolution

    • Search patterns: no source code, out of disk, out of memory, 403, C# compiler, analysis too long, fewer lines, Kotlin, extraction errors, debug logging, SARIF upload, SARIF limits

  • references/alert-management.md — Alert severity, triage, Copilot Autofix, and dismissal

    • Search patterns: severity, security severity, CVSS, Copilot Autofix, dismiss, triage, PR alerts, data flow, merge protection, REST API

Files

references/compiled-languages.md

CodeQL Build Modes for Compiled Languages

Detailed reference for how CodeQL handles compiled language analysis, including build modes, autobuild behavior, runner requirements, and hardware specifications.

Build Modes Overview

CodeQL offers three build modes for compiled languages:

ModeDescriptionWhen to Use
noneAnalyze source without building. Dependencies inferred heuristically.Default setup; quick scans; interpreted-like analysis
autobuildAutomatically detect and run the build system.When none produces inaccurate results; when Kotlin code is present
manualUser provides explicit build commands.Complex build systems; autobuild failures; custom build requirements

C/C++

Supported Build Modes

none, autobuild, manual

Default setup mode: none

No Build (none)
  • Infers compilation units through source file extensions

  • Compilation flags and include paths inferred by inspecting the codebase

  • No working build command needed

Accuracy considerations:

  • May be less accurate if code depends heavily on custom macros/defines not in existing headers

  • May miss accuracy when codebase has many external dependencies

Improving accuracy:

  • Place custom macros/defines in header files included by source files

  • Ensure external dependencies (headers) are available in system include directories or workspace

  • Run extraction on the target platform (e.g., Windows runner for Windows projects)

Autobuild

Windows autodetection:

  1. Invoke MSBuild.exe on .sln or .vcxproj closest to root

  2. If multiple files at same depth, attempts to build all

  3. Falls back to build scripts: build.bat, build.cmd, build.exe

Linux/macOS autodetection:

  1. Look for build system in root directory

  2. If not found, search subdirectories for unique build system

  3. Run appropriate configure/build command

Supported build systems: MSBuild, Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, build scripts

Runner Requirements (C/C++)
  • Ubuntu: gcc compiler; may need clang or msvc. Build tools: msbuild, make, cmake, bazel. Utilities: python, perl, lex, yacc.

  • Auto-install dependencies: Set CODEQL_EXTRACTOR_CPP_AUTOINSTALL_DEPENDENCIES=true (enabled by default on GitHub-hosted; disabled on self-hosted). Requires Ubuntu with passwordless sudo apt-get.

  • Windows: powershell.exe in PATH

C#

Supported Build Modes

none, autobuild, manual

Default setup mode: none

No Build (none)
  • Restores dependencies using heuristics from: *.csproj, *.sln, nuget.config, packages.config, global.json, project.assets.json

  • Uses private NuGet feeds if configured for the organization

  • Generates additional source files for accuracy:

    • Global using directives (implicit using feature)

    • ASP.NET Core .cshtml → .cs conversion

Accuracy considerations:

  • Requires internet access or private NuGet feed

  • Multiple versions of same NuGet dependency may cause issues (CodeQL picks newer version)

  • Multiple .NET framework versions may affect accuracy

  • Colliding class names cause missing method call targets

Autobuild

Windows autodetection:

  1. dotnet build on .sln or .csproj closest to root

  2. MSBuild.exe on solution/project files

  3. Build scripts: build.bat, build.cmd, build.exe

Linux/macOS autodetection:

  1. dotnet build on .sln or .csproj closest to root

  2. MSbuild on solution/project files

  3. Build scripts: build, build.sh

Injected Compiler Flags (Manual Builds)

The CodeQL tracer injects these flags into C# compiler invocations:

FlagPurpose
/p:MvcBuildViews=truePrecompile ASP.NET MVC views for security analysis
/p:UseSharedCompilation=falseDisable shared compilation server (required for tracer inspection)
/p:EmitCompilerGeneratedFiles=trueWrite generated source files to disk for extraction

/p:EmitCompilerGeneratedFiles=true may cause issues with legacy projects or .sqlproj files.

Runner Requirements (C#)
  • .NET Core: .NET SDK (for dotnet)

  • .NET Framework (Windows): Microsoft Build Tools + NuGet CLI

  • .NET Framework (Linux/macOS): Mono Runtime (mono, msbuild, nuget)

  • build-mode: none: Requires internet access or private NuGet feed

Go

Supported Build Modes

autobuild, manual (no none mode)

Default setup mode: autobuild

Autobuild

Autodetection sequence:

  1. Invoke make, ninja, ./build, or ./build.sh until one succeeds and go list ./... works

  2. If none succeed, look for go.mod (go get), Gopkg.toml (dep ensure -v), or glide.yaml (glide install)

  3. If no dependency managers found, rearrange directory for GOPATH and use go get

  4. Extract all Go code (similar to go build ./...)

Default setup automatically detects go.mod and installs compatible Go version.

Extractor Options
Environment VariableDefaultDescription
CODEQL_EXTRACTOR_GO_OPTION_EXTRACT_TESTSfalseInclude _test.go files in analysis
CODEQL_EXTRACTOR_GO_OPTION_EXTRACT_VENDOR_DIRSfalseInclude vendor/ directories

Java/Kotlin

Supported Build Modes
  • Java: none, autobuild, manual

  • Kotlin: autobuild, manual (no none mode)

Default setup mode:

  • Java only: none

  • Kotlin or Java+Kotlin: autobuild

If Kotlin code is added to a repo using none mode, disable and re-enable default setup to switch to autobuild.

No Build (none) — Java Only
  • Runs Gradle or Maven for dependency information (not actual build)

  • Queries each root build file; prefers newer dependency versions on clash

  • Uses private Maven registries if configured

Accuracy considerations:

  • Build scripts that can't be queried for dependencies may cause inaccurate guesses

  • Code generated during normal build process will be missed

  • Multiple versions of same dependency (CodeQL picks newer)

  • Multiple JDK versions — CodeQL uses highest found; lower-version files may be partially analyzed

  • Colliding class names cause missing method call targets

Autobuild

Autodetection sequence:

  1. Search root directory for Gradle, Maven, Ant build files

  2. Run first found (Gradle preferred over Maven)

  3. Otherwise, search for build scripts

Build systems: Gradle, Maven, Ant

Runner Requirements (Java)
  • JDK (appropriate version for the project)

  • Gradle and/or Maven

  • Internet access or private artifact repository (for none mode)

Rust

Supported Build Modes

none, autobuild, manual

Default setup mode: none

Swift

Supported Build Modes

autobuild, manual (no none mode)

Default setup mode: autobuild

Runner requirement: macOS runners only. Not supported on Actions Runner Controller (ARC) — Linux only.

macOS runners are more expensive; consider scanning only the build step to optimize cost.

Multi-Language Matrix Examples

Mixed Build Modes
strategy:
  fail-fast: false
  matrix:
    include:
      - language: c-cpp
        build-mode: manual
      - language: csharp
        build-mode: autobuild
      - language: java-kotlin
        build-mode: none
Conditional Manual Build Steps
steps:
  - name: Checkout
    uses: actions/checkout@v4

  - name: Initialize CodeQL
    uses: github/codeql-action/init@v4
    with:
      languages: ${{ matrix.language }}
      build-mode: ${{ matrix.build-mode }}

  - if: matrix.build-mode == 'manual'
    name: Build C/C++ code
    run: |
      make bootstrap
      make release

  - name: Perform CodeQL Analysis
    uses: github/codeql-action/analyze@v4
    with:
      category: "/language:${{ matrix.language }}"
OS-Specific Runners
strategy:
  fail-fast: false
  matrix:
    include:
      - language: javascript-typescript
        build-mode: none
        runner: ubuntu-latest
      - language: swift
        build-mode: autobuild
        runner: macos-latest
      - language: csharp
        build-mode: autobuild
        runner: windows-latest

jobs:
  analyze:
    runs-on: ${{ matrix.runner }}

Hardware Requirements

Codebase SizeLines of CodeRAMCPU CoresDisk
Small< 100K8 GB+2SSD, ≥14 GB
Medium100K – 1M16 GB+4–8SSD, ≥14 GB
Large> 1M64 GB+8SSD, ≥14 GB
Performance Tips
  • Use SSD storage for all codebase sizes

  • Ensure enough disk space for checkout + build + CodeQL data

  • Use --threads=0 to use all available CPU cores

  • Enable dependency caching to reduce analysis time

  • Consider none build mode where accuracy is acceptable — significantly faster than autobuild

Dependency Caching

Advanced Setup Workflows
- uses: github/codeql-action/init@v4
  with:
    languages: java-kotlin
    dependency-caching: true
ValueBehavior
false / none / offDisabled (default for advanced setup)
restoreRestore existing caches only
storeStore new caches only
true / full / onRestore and store caches

Default setup on GitHub-hosted runners has caching enabled automatically.

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of VeVarunSharmaVeVarunSharma
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/codeql · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
VeVarunSharma

AutoGineer is not affiliated with or endorsed by VeVarunSharma or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download codeql.zip