semgrep

Run coordinated Semgrep static analysis scans to identify vulnerabilities, secrets, and bug patterns.

140|20|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/zekiriabd/SDD-Pro --skill semgrep-zekiriabd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semgrep
Source: https://github.com/zekiriabd/SDD-Pro/tree/main/.sdd/skills/semgrep
Command: npx skills add https://github.com/zekiriabd/SDD-Pro --skill semgrep-zekiriabd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates static security analysis so you can identify vulnerabilities, secrets, bugs, and cross-file data-flow issues without manually configuring and running multiple Semgrep scans.

Core Features & Use Cases

  • Parallel Multi-Language Scanning: Detects supported languages and runs Semgrep rulesets concurrently through specialized scanner agents.
  • Security-Focused Coverage: Combines official, infrastructure, framework-specific, and third-party rulesets, including security audits and secrets detection.
  • Controlled, Auditable Workflow: Checks Semgrep Pro availability, requires explicit approval of the scan plan, disables telemetry, preserves raw results, and merges findings into SARIF.
  • Use Case: Before a production release, scan a full-stack repository for high-confidence vulnerabilities, hardcoded credentials, insecure configurations, and language-specific security flaws.

Quick Start

Ask the Semgrep skill to scan your codebase for security vulnerabilities and present the proposed rulesets and scan plan for approval.

Frequently Asked Questions about semgrep

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

FAQPage Schema
How do I automate static analysis for vulnerabilities in a multi-language codebase?

You can automate static analysis by running parallel Semgrep scans that detect supported languages and concurrently apply coordinated security rulesets to identify vulnerabilities across the codebase.

What is the best way to detect hardcoded secrets and security flaws before a production release?

The best way to detect hardcoded secrets and security flaws before release is combining official, infrastructure, and framework-specific rulesets through parallel Semgrep scans to uncover high-confidence vulnerabilities and insecure configurations.

Can I perform cross-file analysis to track data-flow issues without manual configuration?

You can perform cross-file analysis for data-flow issues by checking for Semgrep Pro availability, approving an explicit scan plan, and running rulesets to identify complex vulnerabilities across multiple files.

Do I need the Semgrep CLI installed to scan my repository for security vulnerabilities?

Yes, the Semgrep CLI is required to scan your repository, as the workflow relies on executing telemetry-disabled commands and merging the resulting vulnerability findings into SARIF format.

How does SARIF result merging work when running parallel vulnerability scanning?

SARIF result merging works by preserving raw findings from multiple parallel scanner tasks and combining them into a unified SARIF report, ensuring an auditable workflow without transmitting telemetry data.

What are the limitations of using static analysis for security audits?

Limitations of static analysis for security audits include the requirement to explicitly approve the scan plan and the need for Semgrep Pro to perform advanced cross-file analysis, focusing primarily on medium-to-critical vulnerability assessments.