Codeql
GitHubOfficialFirst committed by VeVarunSharmaDistributed by GitHub
- Skill
- Tool integration
- Security
- MIT
- No issues found
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
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/github/codeql/downloadUnzip 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.ymlGitHub Actions workflowChoosing 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:
| Language | Identifier | Alternatives |
|---|---|---|
| C/C++ | c-cpp | c, cpp |
| C# | csharp | — |
| Go | go | — |
| Java/Kotlin | java-kotlin | java, kotlin |
| JavaScript/TypeScript | javascript-typescript | javascript, typescript |
| Python | python | — |
| Ruby | ruby | — |
| Rust | rust | — |
| Swift | swift | — |
| GitHub Actions | actions | — |
Alternative identifiers are equivalent to the standard identifier (e.g.,
javascriptdoes 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
nonebuild mode for most languages.Advanced setup — Create a
.github/workflows/codeql.ymlfile 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 UTCpush— scans on every push to specified branches; results appear in Security tabpull_request— scans PR merge commits; results appear as PR check annotationsschedule— 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-ignorecontrols 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-actionStep 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: noneFor compiled languages, set the appropriate build-mode:
none— no build required (supported for C/C++, C#, Java, Rust)autobuild— automatic build detectionmanual— 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 coveragesecurity-and-quality— security plus code quality queriesCustom 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.ymlStep 7: Manual Build Steps (Compiled Languages)
If autobuild fails or custom build commands are needed:
- language: c-cpp
build-mode: manualThen add explicit build steps between init and analyze:
- if: matrix.build-mode == 'manual'
name: Build
run: |
make bootstrap
make releaseCore 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 languagesAlways 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=srcFor 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.sarifCommon 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.sarifRequires GITHUB_TOKEN environment variable with security-events: write permission.
CLI Server Mode
To avoid repeated JVM initialization when running multiple commands:
codeql execute cli-serverFor detailed CLI command reference, search
references/cli-commands.md.
Alert Management
Severity Levels
Alerts have two severity dimensions:
Standard severity:
Error,Warning,NoteSecurity 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/highseverity alertsConfigure 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.qlCreating 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 publishCodeQL 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-queriesCode 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
| Problem | Solution |
|---|---|
| Workflow not triggering | Verify on: triggers match event; check paths/branches filters; ensure workflow exists on target branch |
Resource not accessible error | Add security-events: write and contents: read permissions |
| Autobuild failure | Switch to build-mode: manual and add explicit build commands |
| No source code seen | Verify --source-root, build command, and language identifier |
| C# compiler failure | Check for /p:EmitCompilerGeneratedFiles=true conflicts with .sqlproj or legacy projects |
| Fewer lines scanned than expected | Switch from none to autobuild/manual; verify build compiles all source |
| Kotlin in no-build mode | Disable and re-enable default setup to switch to autobuild |
| Cache miss every run | Verify dependency-caching: true on init action |
| Out of disk/memory | Use larger runners; reduce analysis scope via paths config; use build-mode: none |
| SARIF upload fails | Ensure token has security-events: write; check 10 MB file size limit |
| SARIF results exceed limits | Split across multiple uploads with different --sarif-category; reduce query scope |
| Two CodeQL workflows | Disable default setup if using advanced setup, or remove old workflow file |
| Slow analysis | Enable 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 Size | RAM | CPU |
|---|---|---|
| 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@v4For 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 optionsSearch patterns:
trigger,schedule,paths-ignore,db-location,model packs,alert severity,merge protection,concurrency,config file
references/cli-commands.md— Complete CodeQL CLI command referenceSearch 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 supportSearch 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 languageSearch patterns:
C/C++,C#,Java,Go,Rust,Swift,autobuild,build-mode,hardware,dependency caching
references/troubleshooting.md— Comprehensive error diagnosis and resolutionSearch 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 dismissalSearch patterns:
severity,security severity,CVSS,Copilot Autofix,dismiss,triage,PR alerts,data flow,merge protection,REST API
Files
- ATTRIBUTION.mdAdded by AutoGineer855 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md13.2 KiB
- references/alert-management.md6.3 KiB
- references/cli-commands.md8.1 KiB
- references/compiled-languages.md9.1 KiB
- references/sarif-output.md9.7 KiB
- references/troubleshooting.md8.9 KiB
- references/workflow-configuration.md8.5 KiB
references/alert-management.md
CodeQL Alert Management Reference
Guide for understanding, triaging, dismissing, and resolving code scanning alerts generated by CodeQL.
Alert Severity Levels
Standard Severity
All code scanning alerts have one of these severity levels:
| Level | Description |
|---|---|
Error | High-confidence, high-impact issues that should be fixed |
Warning | Moderate-confidence or moderate-impact issues |
Note | Low-confidence or informational findings |
Security Severity
Security alerts additionally have a security severity derived from CVSS scores:
| Level | CVSS Score Range | Description |
|---|---|---|
Critical | > 9.0 | Severe vulnerabilities requiring immediate attention |
High | 7.0 – 8.9 | Significant vulnerabilities that should be prioritized |
Medium | 4.0 – 6.9 | Moderate vulnerabilities to address in normal workflow |
Low | 0.1 – 3.9 | Minor issues with limited security impact |
When a security severity is present, it takes precedence over the standard severity for display and sorting.
How Security Severity Is Calculated
For each CodeQL security query added to the Default or Extended suite:
All CVEs matching the query's CWE tags are identified
The 75th percentile of CVSS scores for those CVEs is calculated
That score becomes the query's security severity
The numerical score maps to Critical/High/Medium/Low per CVSS definitions
Alert Labels
Alerts in non-application code receive category labels:
| Label | Description |
|---|---|
| Generated | Code generated by the build process |
| Test | Test code (detected by file path) |
| Library | Library or third-party code |
| Documentation | Documentation files |
These labels are assigned automatically based on file paths. They cannot be manually overridden.
Alert Triage in Pull Requests
How PR Alerts Work
Alerts appear as annotations in the Conversation tab and Files changed tab
The Code scanning results check summarizes all findings
Alerts only appear in a PR if ALL identified lines exist in the PR diff
New alerts on changed lines are shown; pre-existing alerts are not
PR Check Failure Behavior
By default, the check fails if alerts have severity of error, critical, or high. Override this threshold via repository Settings → Rules → Rulesets → Code scanning.
Merge Protection
Configure rulesets to block PR merging when:
A required tool finds alerts matching the severity threshold
A required tool's analysis is still in progress
A required tool is not configured for the repository
Copilot Autofix
GitHub Copilot Autofix automatically generates fix suggestions for CodeQL alerts in pull requests.
Availability
Free for all public repositories
Available for private repos with GitHub Code Security license
No Copilot subscription required
Supports a subset of CodeQL queries (not all)
How It Works
Code scanning detects an alert in a PR
Alert information is sent to the LLM for analysis
Fix suggestions are posted as PR comments with inline code changes
Developers review, edit, and commit the suggested fix
Using Autofix Suggestions
Click Edit to apply the fix directly on GitHub or via GitHub CLI
Use View autofix patch to apply locally
Always review and test the fix before committing
The fix may include changes to files not in the original PR diff (e.g., adding a dependency to
package.json)
Dismissing Autofix
Click Dismiss suggestion on the comment to reject a suggestion.
Dismissing Alerts
When to Dismiss
Dismiss alerts when:
The finding is a false positive (code uses a pattern CodeQL doesn't recognize as safe)
The code is used only for testing and risk is acceptable
The effort to fix is greater than the benefit
Dismissal Reasons
Choose the appropriate reason — it affects whether the query continues running:
| Reason | When to Use |
|---|---|
| False positive | The alert is incorrect; the code is actually safe |
| Won't fix | The risk is accepted or the code is being deprecated |
| Used in tests | The vulnerable pattern is only in test code |
Dismissal Comments
Add a comment explaining the dismissal rationale
Comments are stored in the alert timeline for audit/compliance
Accessible via REST API at
alerts/{alert_number}→dismissed_comment
Contributing Improvements
For false positives from unsupported sanitization libraries, consider contributing to the CodeQL repository to improve analysis accuracy.
Resolving Alerts
Fix and Re-scan
Fix the vulnerability in the source code
Commit and push the changes
The next code scanning run will verify the fix
Alert is automatically closed when the fix is confirmed
Removing Stale Configurations
If alerts persist from old/disabled configurations:
Navigate to the alert's Affected branches section
Identify stale configurations
Delete the stale configuration to remove outdated alerts
Alert Data Flow
For path-problem queries, alerts include data flow information:
Source — where untrusted data enters (e.g., user input)
Sink — where the data is used unsafely (e.g., SQL query, HTML output)
Path — the intermediate steps data takes from source to sink
Click Show paths on alert annotations to visualize the full data flow.
Multi-Configuration Alerts
When multiple code scanning configurations analyze the same file:
The same problem detected by the same query appears as a single alert
The Affected branches section shows which configurations found the alert
Different configurations may show different statuses
Re-run out-of-date configurations to synchronize alert statuses
Viewing Alerts
Repository Security Tab
Navigate to Security → Code scanning alerts
Filter by: tool, severity, rule, branch, state
Click an alert to see full details, affected branches, and data flow
Pull Request Checks
View Code scanning results check in the PR
Click View all branch alerts for the full alert list
Annotations appear inline in Files changed
REST API
GET /repos/{owner}/{repo}/code-scanning/alerts— list alertsGET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}— get alert detailsPATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}— update alert status
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
VeVarunSharma
- 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