skills.rest
rohunj
rohunjCOMMUNITY
Explore all skills by this author →
Website𝕏@rohunjauharGitHub

secrets-gitleaks

Detect hardcoded secrets in repositories with Gitleaks scans.

232|38|Updated Jan 18, 2026
Search Tags:#security#secrets#pre-commit#devsecops#ci-cd#secret-detection#gitleaks
One-click install
npx skills add https://github.com/rohunj/claude-build-workflow --skill secrets-gitleaks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-gitleaks
Source: https://github.com/rohunj/claude-build-workflow/tree/main/skills/security/secrets-gitleaks
Command: npx skills add https://github.com/rohunj/claude-build-workflow --skill secrets-gitleaks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Hardcoded secrets in codebases expose credentials, create security incidents, and complicate compliance. This Skill provides automated detection and remediation guidance using Gitleaks to help teams identify and manage secrets before they reach production.

Core Features & Use Cases

  • Automated secret detection across repositories, commits, and CI pipelines.
  • Pre-commit protection to prevent secret leakage before code is committed.
  • Remediation guidance and best practices for rotating and removing exposed credentials.
  • Use case: Scan a legacy repository, identify API keys and passwords, rotate them, and implement proper secret management.

Quick Start

Run a secret-scan across a repository to identify exposed credentials and follow remediation steps provided in the guidance.

Frequently Asked Questions about secrets-gitleaks

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

FAQPage Schema
How do I detect hardcoded secrets in a repository before they are committed?▼

Scan full repository histories to identify hardcoded secrets and credentials. This Skill uses Gitleaks to detect exposed API keys and passwords across past commits, then provides remediation guidance for rotating and removing them.

Can I scan for hardcoded secrets in my CI/CD pipelines?▼

Yes, you can enforce credential hygiene by integrating secret detection in CI/CD pipelines. This automated scanning identifies exposed credentials during continuous integration to prevent leakage before reaching production environments.

What is the best way to scan a legacy repository for exposed API keys and passwords?▼

Scan a legacy repository using automated secret detection across the full commit history. This identifies exposed API keys and passwords, providing remediation guidance and best practices for rotating compromised credentials.

How do I configure pre-commit hooks to prevent secret leakage in development workflows?▼

Configure pre-commit hooks using provided integration templates and scanning rules. This prevents secret leakage by blocking hardcoded credentials from entering the repository during local development workflows.

What remediation steps should I take after finding hardcoded secrets in my codebase?▼

Follow remediation guidance to rotate and remove exposed credentials after detecting hardcoded secrets. This prevents security incidents by replacing compromised credentials and implementing proper secret management practices.

Related Skills

Explore More Legal & Compliance Skills→
balsm-healthbalsm-health
2

implementing-secrets-scanning-in-ci-cd

Automate hardcoded secret detection in CI/CD pipelines with gitleaks and trufflehog.

Official
Advanced
GoldenWing-360GoldenWing-360
15

secret-hygiene

Detect leaked credentials in git history and local files.

Official
Intermediate
arbazkhan971arbazkhan971
26

secrets

Detect exposed secrets and rotate credentials into secret managers.

Community
Advanced
endorlabsendorlabs
2

endor-secrets

Scan codebases for exposed secrets and API keys via MCP.

Official
Intermediate