skills.rest
Obsidian-Owl
Obsidian-OwlOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gate-security

Scan changed files for leaked secrets and injection patterns using SAST tools.

9|1|Updated Feb 9, 2026
Search Tags:#security#vulnerability#injection#secrets#SAST#code scanning
One-click install
npx skills add https://github.com/Obsidian-Owl/specwright --skill gate-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gate-security
Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/gate-security
Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill gate-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill proactively identifies and flags security risks within your codebase, preventing the introduction of secrets, injection vulnerabilities, and sensitive data exposure.

Core Features & Use Cases

  • Secret Detection: Scans for leaked API keys, tokens, and passwords.
  • Vulnerability Scanning: Analyzes code for common injection patterns (SQL, XSS, etc.).
  • Sensitive Data Exposure: Checks for unintended exposure of private information.
  • Use Case: Before merging a pull request, run this gate to ensure no accidental credential leaks or new security flaws are introduced into the main branch.

Quick Start

Run the security gate to scan all changed files for potential vulnerabilities.

Frequently Asked Questions about gate-security

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

FAQPage Schema
How do I scan changed files for leaked secrets before a pull request merge?▼

Scanning changed files for leaked secrets before a pull request merge involves running a security gate to detect API keys, tokens, and passwords. This prevents accidental credential leaks from entering the main branch.

How does static analysis detect injection vulnerabilities in my codebase?▼

Static analysis detects injection vulnerabilities by using SAST tools and LLM analysis to evaluate code patterns. This process identifies common injection risks like SQL and XSS during pre-commit checks.

What is the best way to prevent sensitive data exposure in CI/CD pipelines?▼

Preventing sensitive data exposure in CI/CD pipelines requires running a security gate to check for unintended private information leaks. This ensures sensitive data is flagged before code integration.

Do I need to configure SAST tools for code review security checks?▼

Configuring specific SAST tools is required for code review security checks. This configuration enables the system to generate evidence and adhere to security protocols while analyzing changed files.

Can LLM analysis identify API keys and tokens alongside static application security testing?▼

LLM analysis supplements static application security testing by identifying leaked API keys and tokens. Combined, they provide thorough vulnerability scanning and secret detection for changed files.

Related Skills

Explore More Software Engineering Skills→
camoneartcamoneart
5

sast-configuration

Configure Semgrep, SonarQube, and CodeQL for automated vulnerability detection in CI/CD pipelines.

Community
Advanced
DITEKmaxDITEKmax

find-bugs

Analyze Git branch diffs for bugs, security vulnerabilities, and code quality issues.

Community
Advanced
aggelosChatziioannouaggelosChatziioannou

Code Reviewer

Analyze code for bugs, security vulnerabilities, and style issues before commits.

Community
Intermediate
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced