ethereal-security-scan

Scan staged changes for hardcoded secrets and unsafe patterns before commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hardcoded secrets, API keys, and unsafe coding patterns in code changes pose a serious security risk and can lead to data breaches and compliance issues.

Core Features & Use Cases

  • Pre-commit scans detect hardcoded secrets and keys in staged files across languages.
  • Regex-based detection helps prevent credential leakage during commits.
  • Use cases include preventing secret leakage in orchestrator and related services during development and code review.

Quick Start

Run a pre-commit security scan on your staged changes to identify secrets and risky patterns before committing.

Frequently Asked Questions about ethereal-security-scan

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

FAQPage Schema
How do I prevent hardcoded API keys from being committed to my repository?

Pre-commit security scans identify and block hardcoded API keys in staged changes before commits. By applying regex-based detection across all changed files, the scan prevents credential leakage during development and code review workflows.

What is a pre-commit hook for detecting secrets and unsafe patterns?

A pre-commit hook for detecting secrets scans staged files using regex-based pattern matching to find hardcoded credentials and unsafe database queries. It blocks the commit process if risky patterns are found, ensuring codebase security before changes are recorded.

Can I run a static analysis scan on staged changes across multiple file types?

Yes, static analysis scans apply project file globbing to evaluate all changed files across the repository regardless of language. This catches secrets, API keys, and unsafe database queries within the codebase during pre-commit and pull request workflows.

Does pre-commit secret scanning work with pull request workflows?

Pre-commit secret scanning works with pull request workflows by applying regex-based scans to changed files. It detects and blocks hardcoded secrets, API keys, and unsafe patterns, providing safe reporting to prevent credential leakage during code review.

What are the limitations of regex-based secret detection in code scans?

Regex-based secret detection limitations include reliance on predefined patterns, which may miss novel or obfuscated credentials. It scans staged changes and uses safe reporting to catch known unsafe database queries, but cannot identify complex logic flaws or dynamically generated API keys.