update-codeql-query-dataflow-swift

Migrate Swift CodeQL dataflow queries from v1 APIs to v2 DataFlow::ConfigSig.

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-swift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-codeql-query-dataflow-swift
Source: https://github.com/advanced-security/codeql-development-mcp-server/tree/main/.github/skills/update-codeql-query-dataflow-swift
Command: npx skills add https://github.com/advanced-security/codeql-development-mcp-server --skill update-codeql-query-dataflow-swift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates Swift CodeQL dataflow queries from the legacy v1 API to the modern v2 DataFlow::ConfigSig workflow, ensuring behavior remains stable through test-driven migration.

Core Features & Use Cases

  • Module-based migration: convert v1 DataFlow::Configuration-backed queries to the v2 DataFlow::ConfigSig module pattern.
  • Test-driven validation: establish baselines and verify equivalence with existing unit tests.
  • Swift-specific dataflow handling: address Swift flow sources, sinks, barriers, and framework patterns (e.g., Alamofire, Realm, CryptoKit).

Quick Start

Migrate your first Swift dataflow query by following this guide and run the test suite to verify equivalence.

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

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

FAQPage Schema
How do I migrate Swift CodeQL dataflow queries from v1 TaintTracking to v2 ConfigSig?

Migrate Swift CodeQL dataflow queries by converting legacy v1 TaintTracking::Configuration APIs to the modern v2 DataFlow::ConfigSig module pattern while preserving original query results.

What is the DataFlow::ConfigSig migration process for Swift taint-tracking queries?

The DataFlow::ConfigSig migration replaces v1 TaintTracking::Configuration structures with a module-based v2 workflow, updating Swift-specific flow sources, sinks, and barriers to maintain equivalent taint-tracking behavior.

Do I need existing unit tests to migrate Swift CodeQL dataflow APIs to v2?

Yes, the migration is test-driven and requires existing Swift CodeQL queries with unit tests to establish baselines and verify behavioral equivalence before and after adopting the v2 DataFlow::ConfigSig pattern.

Can I migrate Swift CodeQL queries that use framework-specific dataflow patterns like Alamofire or Realm?

Yes, the migration handles Swift-specific dataflow changes across frameworks like Alamofire, Realm, and CryptoKit, adapting their flow sources, sinks, and barrier patterns to the v2 ConfigSig workflow.

Why are my Swift CodeQL dataflow query results changing after a v1 to v2 migration?

If Swift CodeQL dataflow results change after migration, the v2 DataFlow::ConfigSig conversion may have improperly mapped Swift-specific flow sources, sinks, or barriers, requiring unit test validation to restore equivalence.

What's the best way to validate CodeQL Swift dataflow query equivalence during a v2 migration?

Validate CodeQL Swift dataflow query equivalence by establishing baseline test results with existing unit tests and verifying that the v2 ConfigSig migration preserves identical query outcomes.