security-gitleaks

Scan files, git history, and staged changes for leaked secrets.

Updated Feb 12, 2026

Search Tags:#ci/cd #security #compliance #secrets #pre-commit #gitleaks

Ready to run

npx skills add https://github.com/kobogithub/knowledge --skill security-gitleaks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-gitleaks
Source: https://github.com/kobogithub/knowledge/tree/main/skills/security-gitleaks
Command: npx skills add https://github.com/kobogithub/knowledge --skill security-gitleaks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents sensitive information like API keys, passwords, and tokens from being accidentally committed to your code repositories, safeguarding your projects from security breaches.

Core Features & Use Cases

Secret Detection: Scans current files, git history, and staged changes for secrets.
Prevention: Integrates with pre-commit hooks and CI/CD pipelines to stop secrets before they are committed.
Customizable Rules: Allows defining specific rules and allowlists for your project's needs (e.g., Supabase keys, JWT secrets).
Use Case: Automatically scan all new commits for accidentally exposed AWS access keys and fail the build if any are found.

Quick Start

Run a basic Gitleaks scan on the current directory to detect secrets.

Frequently Asked Questions about security-gitleaks

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

FAQPage Schema

How do I scan git history for exposed API keys and passwords?▼

To scan git history for exposed API keys, the tool analyzes current files, git history, and staged changes to detect secrets. It automatically identifies sensitive information like tokens to prevent accidental commits into your repositories.

Can I integrate secret detection into CI/CD pipelines and pre-commit hooks?▼

Yes, you can integrate secret detection into CI/CD pipelines and pre-commit hooks to stop secrets before they are committed. This proactive security approach automatically fails builds if exposed credentials are found.

How do I configure custom rules and allowlists for specific secrets like Supabase keys?▼

Configuring custom rules and allowlists for specific secrets like Supabase keys and JWT secrets involves defining specific rule configurations. This allows you to tailor detection to your project needs and allowlist specific credentials.

What's the best way to prevent sensitive information from being committed to repositories?▼

The best way to prevent sensitive information from being committed to repositories is to scan current files and staged changes using pre-commit hooks. This blocks API keys, passwords, and tokens from entering your codebase.

Does this secret scanning tool work without additional dependencies?▼

Yes, the secret scanning tool works without additional dependencies. It operates independently to scan directories and git history for sensitive information, requiring no external modules to function.