security-scan

Scan code changes for secrets, dependency vulnerabilities, and injection risks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/meriley/claude-code-skills --skill security-scan-meriley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/meriley/claude-code-skills/tree/main/skills/security-scan
Command: npx skills add https://github.com/meriley/claude-code-skills --skill security-scan-meriley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically scans your code for security vulnerabilities, secrets, and potential injection risks, ensuring that no sensitive information or insecure code is committed.

Core Features & Use Cases

  • Secrets Detection: Identifies hardcoded API keys, passwords, and tokens.
  • Vulnerability Scanning: Checks for known security flaws in project dependencies.
  • Injection Risk Analysis: Flags patterns indicative of SQL or command injection.
  • Use Case: Before committing code, this skill runs automatically via safe-commit to prevent accidental exposure of credentials or the introduction of vulnerable libraries.

Quick Start

Let safe-commit automatically invoke the security scan before your next commit.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I scan code for security vulnerabilities before a commit?

Secrets detection identifies hardcoded API keys, passwords, and tokens by scanning code changes before they are committed. This prevents accidental exposure of sensitive information by enforcing security policies during the commit workflow.

Can I automatically block commits that contain hardcoded secrets?

Dependency vulnerability scanning checks project dependencies for known security flaws during the code change process. It enforces security policies by halting commits that introduce vulnerable libraries into the project.

How does injection risk analysis work for SQL or command vulnerabilities?

No additional dependencies are required to use this security scanning Skill. It operates independently to perform comprehensive vulnerability analysis, secrets detection, and injection risk identification on your code changes.

What is the best way to prevent accidental credential exposure in code changes?

The best way to prevent accidental credential exposure is using automated secrets detection during commit workflows. This Skill enforces security policies by halting commits that expose sensitive information like hardcoded API keys or tokens.