skills.rest
zcaceres
zcaceresCOMMUNITY
Explore all skills by this author →
Website𝕏@zachcaceresGitHub

security-gitleaks

Scan git history and working directories for sensitive credentials using Gitleaks and Git.

7|Updated May 28, 2026
Search Tags:#git#security#compliance#secrets#ci-cd#gitleaks
One-click install
npx skills add https://github.com/zcaceres/skills --skill security-gitleaks-zcaceres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-gitleaks
Source: https://github.com/zcaceres/skills/tree/main/skills/security-gitleaks
Command: npx skills add https://github.com/zcaceres/skills --skill security-gitleaks-zcaceres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill prevents accidental credential exposure by scanning your repository for secrets before they are committed or pushed, protecting you from the severe security risks of leaked API keys and passwords.

Core Features & Use Cases

  • Baseline Scanning: Performs a comprehensive audit of your entire git history and working tree to identify existing leaks before applying new security measures.
  • Proactive Protection: Installs a local pre-commit hook and a CI workflow to ensure that no new secrets are introduced in future commits or pull requests.
  • Customizable Rules: Supports extending default security rules with project-specific patterns and path-based allowlists to minimize false positives.

Quick Start

Activate the security-gitleaks skill by typing /security-gitleaks in your agent chat to begin the repository audit and setup process.

Frequently Asked Questions about security-gitleaks

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

FAQPage Schema
How do I scan my git repository for accidentally committed secrets and API keys?▼

You can scan a git repository for secrets by running a comprehensive baseline audit of your entire git history and working tree to identify existing leaked credentials before enforcing new security measures.

How do I prevent secrets from being committed to git in my CI/CD pipeline?▼

To prevent secrets from being committed in a CI/CD pipeline, this skill installs a pre-commit hook and a CI workflow to ensure no new sensitive credentials are introduced in future commits or pull requests.

Can I customize secret scanning rules to reduce false positives in my project?▼

Yes, you can customize secret scanning rules by extending the default security configurations with project-specific patterns and path-based allowlists to minimize false positives during credential detection.

Do I need to install gitleaks and git separately to scan for sensitive credentials?▼

Yes, you need both the gitleaks binary and git installed, because the skill requires these dependencies to perform comprehensive secret detection and validation across your local environment and CI/CD pipelines.

What is the best way to audit existing git history for hidden sensitive credentials?▼

The best way to audit git history for hidden sensitive credentials is performing a baseline scan, which comprehensively checks your entire repository history and working directory to identify any accidental exposures.

Related Skills

Explore More Software Engineering Skills→
wewetv1987-cellwewetv1987-cell

git-helper

Manage Git repository status, pull, push, branch, and log operations.

Community
Basic
ArogyaReddyArogyaReddy

sast-configuration

Configure Semgrep, SonarQube, and CodeQL for multi-language CI/CD security scanning.

Community
Advanced
rohunjrohunj
232

secrets-gitleaks

Detect hardcoded secrets in repositories with Gitleaks scans.

Community
Advanced
zebbernzebbern
5

github-recon

Scan Git repositories and GitHub organizations for exposed API keys and credentials.

Community
Advanced