codeql-semgrep

Combine CodeQL data-flow queries and Semgrep rules to detect vulnerabilities.

31|8|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill codeql-semgrep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codeql-semgrep
Source: https://github.com/itallstartedwithaidea/agent-skills/tree/main/skills/security/codeql-semgrep
Command: npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill codeql-semgrep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of missing security vulnerabilities in code by combining deep data-flow analysis with structural pattern matching, producing actionable remediation guidance that can be enforced in CI/CD.

Core Features & Use Cases

  • Deep vulnerability detection with CodeQL: Traces data flow from sources (e.g., user input) to sinks (e.g., dangerous operations) to catch issues regex-based scanners often miss.
  • Structural and rule-based security coverage with Semgrep: Identifies syntactic and architectural anti-patterns via custom semgrep rules, including invariants like “auth on every route” or “no stack trace leakage.”
  • Project-specific security enforcement: Lets the agent generate custom CodeQL queries and Semgrep rules tailored to your codebase patterns and security requirements, then run scans as CI/CD gates.

Use case example: An AI-assisted developer submits a PR that introduces potential SQL injection and a route missing authentication; this skill generates/uses CodeQL data-flow analysis plus Semgrep custom rules to identify both issues, deduplicate findings, prioritize them, and fail the CI gate on ERROR findings.

Quick Start

Use the codeql-semgrep skill to run static security analysis on your repository and produce a prioritized remediation report from CodeQL queries and Semgrep rules.

Frequently Asked Questions about codeql-semgrep

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

FAQPage Schema
How do I trace user input to dangerous operations to find deep security vulnerabilities?

Static security analysis traces data flow from sources to sinks using CodeQL queries to detect deep vulnerabilities that regex-based scanners often miss. It identifies complex injection paths by analyzing code semantics and data movement.

What is the best way to enforce custom security rules and architectural invariants in CI/CD?

You can enforce custom security rules in CI/CD by generating Semgrep rules to match syntactic anti-patterns and invariants like missing authentication on routes. The scan then acts as a pass/fail gate during pull requests.

Can I use static analysis to scan AI-generated code for security anti-patterns?

Yes, static analysis applies to both AI-generated and human-written code by running vulnerability scans with custom CodeQL queries and Semgrep rules. It identifies security anti-patterns and traces sources-to-sinks before merge.

How do I deduplicate and prioritize findings from CodeQL and Semgrep scans?

Static analysis deduplicates and prioritizes findings by combining CodeQL data-flow results with Semgrep rule matches, generating a prioritized remediation report with CWE-aligned metadata for actionable guidance.

Does taint tracking work for identifying vulnerabilities regex-based scanners miss?

Taint tracking via CodeQL data-flow queries traces untrusted user input from sources to dangerous sinks, catching deep vulnerabilities that standard structural pattern matching and regex-based scanners often miss.