skills.rest
patricio0312rev
patricio0312revCOMMUNITY
Explore all skills by this author →
Website𝕏@patricio0312revGitHub

secrets-scanner

Detect leaked credentials in codebases across pre-commit hooks and CI pipelines.

5|Updated Dec 31, 2025
Search Tags:#security#secrets#credentials#pre-commit#scanning#ci
One-click install
npx skills add https://github.com/patricio0312rev/skillset --skill secrets-scanner-patricio0312rev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-scanner
Source: https://github.com/patricio0312rev/skillset/tree/main/templates/security/secrets-scanner
Command: npx skills add https://github.com/patricio0312rev/skillset --skill secrets-scanner-patricio0312rev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects leaked credentials in codebases and prevents secret exposure.

Core Features & Use Cases

  • Pre-commit integration to catch secrets before commit
  • CI pipeline scanning and remediation guidance
  • Comprehensive secret-detection patterns and best practices

Quick Start

Install and enable the scanner across your repository in one step.

Frequently Asked Questions about secrets-scanner

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

FAQPage Schema
How do I scan for leaked secrets and credentials in my codebase?▼

You scan for leaked secrets by applying configurable secret-detection patterns across your repository, which identifies exposed credentials and provides remediation steps to prevent leaks.

How do I set up a pre-commit hook to catch secrets before committing code?▼

A pre-commit hook catches secrets by integrating secret scanning directly into your local workflow, detecting leaked credentials in staged files and preventing the commit if exposure is found.

Can I integrate secret scanning into my CI pipelines across different languages?▼

Yes, you can integrate secret scanning into CI pipelines across languages and workflows, applying comprehensive secret-detection patterns to catch leaked credentials during automated builds and provide remediation guidance.

What is the best way to prevent credentials from leaking into version control?▼

The best way to prevent credentials from leaking into version control is combining pre-commit hooks with CI pipeline scanning to detect leaked secrets early and apply remediation steps before exposure.

Does secret scanning support configurable rules for different repository workflows?▼

Yes, secret scanning supports configurable scanning rules tailored to different repository workflows, allowing you to apply specific secret-detection patterns and remediation steps across various languages and environments.

Related Skills

Explore More Software Engineering Skills→
lenadlmlenadlm

requesting-code-review

Scan code commits for security issues and run quality tests.

Community
Advanced
alirezarezvanialirezarezvani
763

secret-scanner

Detect exposed secrets and block commits containing sensitive credentials.

Community
Basic
nsalvacaonsalvacao

Automation Strategies

Automate pre-commit hooks, linters, formatters, security scans, and CI/CD pipelines across Python, JavaScript/TypeScript, Go, and universal stacks.

Community
Advanced
AdeptMindAdeptMind

secret-rotation

Scan codebases for hardcoded secrets and audit rotation policies.

Official
Advanced