update-codeql-query-dataflow-javascript

Migrate CodeQL dataflow queries from v1 to v2 API for JavaScript/TypeScript.

30|3|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/advanced-security/codeql-development-mcp-server --skill update-codeql-query-dataflow-javascript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-codeql-query-dataflow-javascript
Source: https://github.com/advanced-security/codeql-development-mcp-server/tree/main/.github/skills/update-codeql-query-dataflow-javascript
Command: npx skills add https://github.com/advanced-security/codeql-development-mcp-server --skill update-codeql-query-dataflow-javascript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates CodeQL dataflow queries from the legacy v1 API to the modern v2 API for JavaScript and TypeScript projects, enabling modern dataflow patterns while preserving results.

Core Features & Use Cases

  • Migrate configurations from DataFlow::Configuration to DataFlow::ConfigSig modules.
  • Update flow predicates to DataFlow::StateConfigSig and related FlowState usage.
  • Validate query result equivalence with test-driven migration across codebases and frameworks.

Quick Start

Begin by running existing tests to establish a baseline, then migrate API usage step by step.

Frequently Asked Questions about update-codeql-query-dataflow-javascript

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

FAQPage Schema
How do I migrate CodeQL dataflow queries from v1 to v2 for JavaScript?

You can migrate JavaScript CodeQL dataflow by transforming legacy DataFlow::Configuration classes into DataFlow::ConfigSig modules and updating flow predicates to leverage DataFlow::StateConfigSig and FlowState.

What is the CodeQL v2 dataflow API and how does it change TypeScript query development?

The CodeQL v2 dataflow API replaces legacy v1 configurations with DataFlow::ConfigSig modules and FlowState usage, enabling more modular and flexible data flow tracking for TypeScript and JavaScript codebases.

How do I ensure my CodeQL dataflow migration preserves existing query results?

To preserve query result equivalence during CodeQL dataflow migration, apply test-driven development by running existing tests to establish a baseline before stepping through v2 API updates.

Do I need existing v1 dataflow queries before starting a JavaScript CodeQL migration?

Yes, starting a JavaScript CodeQL migration requires existing v1 dataflow JS/TS queries, access to MCP server tooling, and familiarity with v2 API changes such as FlowState and isBarrier.

What should I do if my CodeQL dataflow migration breaks TypeScript query barriers?

If a CodeQL dataflow migration breaks TypeScript query barriers, verify your FlowState implementation and isBarrier configurations to ensure the v2 API correctly preserves flow constraints during the transition.