skills.rest
Probably-Group
Probably-GroupOFFICIAL
Explore all skills by this author →
Website𝕏@problynotingGitHub

secret-scanner

Scan files for exposed secrets and block commits on credential matches.

3|1|Updated Dec 3, 2025
Search Tags:#pre-commit#api keys#security automation#secret scanning#credential detection#git enforcement
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill secret-scanner-probably-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-scanner
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/core/secret-scanner
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill secret-scanner-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secret-scanner prevents accidental credential leaks by stopping commits that include API keys, tokens, passwords, or private keys in files before they reach your repository.

Core Features & Use Cases

  • Secret Detection Patterns: Identifies common real-world credentials such as AWS access keys, GitHub tokens, Stripe live keys, OAuth/client secrets, and private key blocks.
  • Config & Environment Hygiene: Flags risky files like .env and common credential filenames (for example credentials.json) to reduce unintended exposure.
  • Blocking Enforcement: Uses a pre-commit style gate to prevent commits when a secret match is found, requiring manual review and remediation.

Quick Start

Use secret-scanner whenever you are about to commit changes that could contain credentials, and ask the assistant to scan the modified files for exposed secrets and confirm whether the commit should be blocked.

Frequently Asked Questions about secret-scanner

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

FAQPage Schema
How do I prevent API keys and tokens from being accidentally committed to git?▼

To prevent API keys and tokens from being committed to git, you can use a pre-commit style gate that scans modified files for exposed credentials and blocks the commit if a secret match is found.

What types of credentials and sensitive files does secret scanning detect?▼

Secret scanning detects AWS access keys, GitHub tokens, Stripe live keys, OAuth secrets, private key blocks, and risky files like .env and credentials.json to reduce unintended exposure.

How do I scan staged files for exposed secrets before pushing code?▼

You can scan staged files for exposed secrets by asking the assistant to review modified files during editing and staging, applying pattern-based detection to block commits containing credentials.

Does this secret scanner require any external dependencies or pre-commit hooks to work?▼

No external dependencies or pre-commit hooks are required. The scanner operates independently using pattern-based detection to enforce blocking behavior when credentials are identified.

What happens when a secret is detected in my code changes?▼

When a secret is detected in your code changes, the scanner enforces blocking behavior to prevent the commit from proceeding, requiring manual review and remediation of the exposed credential.

Can I use secret scanning for environment files like .env?▼

Yes, you can use secret scanning for environment files like .env. The scanner flags risky credential filenames and config files to minimize repository risk during development workflows.

Related Skills

Explore More Software Engineering Skills→
voidrotvoidrot

secret-scanning

Detects credential leaks in Git repositories and blocks pushes containing secrets.

Community
Advanced
tomascuprtomascupr
68

refire

Apply verified code review findings to git repository files and verify fixes.

Community
Advanced
achmfachmf

vulnerability-scanner

Scan software projects for vulnerabilities, hardcoded secrets, and insecure code patterns.

Community
Advanced
zcacereszcaceres
7

gitleaks

Scan git repositories for exposed credentials using gitleaks.

Community
Advanced