mcaf-dotnet-codeql

Configure CodeQL static analysis for .NET repositories via GitHub Actions or CLI.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-codeql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcaf-dotnet-codeql
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-dotnet-codeql
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-codeql

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for robust security analysis in .NET projects by leveraging the CodeQL ecosystem, ensuring code quality and identifying vulnerabilities.

Core Features & Use Cases

  • CodeQL Integration: Facilitates the use of CodeQL for static analysis of .NET codebases.
  • GitHub Actions Setup: Assists in configuring CodeQL scanning within GitHub Actions workflows.
  • CLI-based Analysis: Supports local CodeQL analysis for development and debugging.
  • Use Case: A development team wants to integrate security scanning into their CI/CD pipeline for a .NET application. This Skill helps them set up CodeQL to automatically scan for vulnerabilities on every commit.

Quick Start

Use the mcaf-dotnet-codeql skill to set up CodeQL for this public .NET repository.

Frequently Asked Questions about mcaf-dotnet-codeql

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

FAQPage Schema
How do I set up CodeQL static analysis for a .NET repository?

To set up CodeQL static analysis for a .NET repository, you configure GitHub Actions workflows or enable CLI-based analysis. This integration applies query packs to automatically identify vulnerabilities and ensure code quality.

Can I use CodeQL code scanning with GitHub Actions for private .NET repositories?

You can use CodeQL code scanning with GitHub Actions for private .NET repositories, but setup requires addressing explicit licensing caveats. The Skill assists in configuring the workflow while respecting these specific licensing requirements.

What is the best way to run local CodeQL analysis on a .NET codebase?

Running local CodeQL analysis on a .NET codebase is best achieved by configuring a CLI-based CodeQL workflow. This approach supports local development and debugging using open-source CodeQL query packs.

Does CodeQL security analysis require any specific dependencies for .NET projects?

CodeQL security analysis for .NET projects operates without external dependencies but requires a GitHub-based or CLI-based CodeQL workflow. It uses CodeQL query packs and respects the repository's existing AGENTS.md commands first.

Are there limitations when using CodeQL for .NET security analysis?

Limitations when using CodeQL for .NET security analysis include explicit licensing caveats for private repositories. The process requires a GitHub-based or CLI-based workflow and prioritizes the repository's existing AGENTS.md commands.