security-watch

Scan code commits for secrets and dangerous patterns.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/CENKSSS/valocase-backend --skill security-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-watch
Source: https://github.com/CENKSSS/valocase-backend/tree/main/.claude/skills/security-watch
Command: npx skills add https://github.com/CENKSSS/valocase-backend --skill security-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Security-watch is designed to prevent the accidental inclusion of secrets and dangerous patterns in code before they are committed.

Core Features & Use Cases

  • Secrets Detection: Identifies API keys, passwords, tokens, and private keys in source code.
  • Dangerous Functions: Flags usage of functions like eval(), Function(), and innerHTML.
  • Injection Vectors: Detects unsanitized template literals in SQL/shell commands.
  • Insecure Config: Alerts for http:// URLs, disabled TLS verification, and * CORS origins.
  • Use Case: Ideal for security-sensitive codebases to catch potential vulnerabilities early.

Quick Start

Activate security scanning with /security-watch.

Frequently Asked Questions about security-watch

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

FAQPage Schema
How do I scan code commits for security vulnerabilities and secrets?

To scan code commits for security vulnerabilities, activate the scanning process to identify and flag common dangerous patterns and secrets in real-time. This prevents accidental inclusion of sensitive data like API keys and tokens before committing.

What types of secrets and dangerous patterns can code scanning detect?

Code scanning detects secrets like API keys, passwords, tokens, and private keys. It also flags dangerous functions such as eval() and innerHTML, unsanitized template literals in SQL or shell commands, and insecure configurations like disabled TLS verification.

How do I prevent accidental secrets in source code before they are committed?

To prevent accidental secrets in source code before committing, use real-time security scanning to monitor and flag sensitive patterns. This catches API keys, passwords, and insecure configurations early in software development environments.

Can code scanning detect insecure configurations like disabled TLS verification and CORS issues?

Yes, code scanning can detect insecure configurations by alerting on http:// URLs, disabled TLS verification, and wildcard CORS origins. It also identifies injection vectors through unsanitized template literals in SQL and shell commands.

Does security scanning work without external dependencies?

Yes, security scanning operates without external dependencies, relying solely on internal scripts to scan and flag issues. This makes it easy to integrate into security-sensitive codebases to catch potential vulnerabilities early.