secret-guard

Block hardcoded credentials and API keys during git commit workflows.

Updated May 5, 2026

Search Tags:#git #devops #security #compliance #secrets #privacy

Ready to run

npx skills add https://github.com/iani-kuli/harness_bro --skill secret-guard-iani-kuli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secret-guard
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/curated/secret-guard
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill secret-guard-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the accidental exposure of sensitive credentials like API keys, tokens, and passwords by blocking them from being committed to version control or pushed to public repositories.

Core Features & Use Cases

Proactive Scanning: Detects hardcoded secrets in code before they are committed or pushed to GitHub.
Defense in Depth: Integrates with git hooks and environment variable best practices to ensure secrets never leave the local environment.
Use Case: If you accidentally paste an OpenAI API key into a Python script, this Skill will identify the pattern and block the commit, prompting you to move the key to an environment variable instead.

Quick Start

Use the secret-guard skill to scan the current directory for any hardcoded credentials or sensitive patterns before committing your changes.

Frequently Asked Questions about secret-guard

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

FAQPage Schema

How do I prevent accidental API key exposure in git commits?▼

To prevent accidental API key exposure in git commits, you can use a scanning tool that integrates with local git hooks to identify and block hardcoded tokens or private keys before they are pushed to a repository.

What is the best way to scan source code for hardcoded secrets before a git push?▼

The best way to scan source code for hardcoded secrets before a git push is to enforce security policies using regex-based scanning tools within your git commit and push workflows, blocking insecure patterns locally.

How do git hooks work to stop sensitive credentials from being committed?▼

Git hooks work to stop sensitive credentials by executing regex-based scanning scripts during the commit and push workflows, detecting insecure patterns like private keys, and blocking the transaction before data leaves the local environment.

Does this secret scanning approach work with environment variables?▼

Yes, this secret scanning approach works with environment variables by detecting hardcoded credentials in your code and prompting you to move them to environment variables, ensuring secrets never leave the local environment.

What types of sensitive patterns can be detected during a git commit?▼

During a git commit, the scanning process can detect sensitive patterns such as hardcoded API keys, tokens, passwords, and private keys using regex-based matching to enforce compliance and prevent data leaks.