secret-guard

Scan staged Git diffs for credentials, PII, and sensitive data.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/oioio-space/unpixel --skill secret-guard-oioio-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-guard
Source: https://github.com/oioio-space/unpixel/tree/main/.claude/skills/secret-guard
Command: npx skills add https://github.com/oioio-space/unpixel --skill secret-guard-oioio-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures no sensitive information is committed to Git or GitHub repositories during code reviews or commits.

Core Features & Use Cases

  • Pre-commit Gate: Blocks commits containing known secrets based on regex/entropy match.
  • AI Review: Checks staged diffs for leaks like credentials, internal IPs, and PII.
  • Use Case: For organizations that need strict adherence to security policies, this skill can help prevent accidental disclosure of sensitive data.

Quick Start

Before committing, run git diff --cached and use the secret-guard skill to scan for potential leaks.

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 secret leakage in GitHub commits?

You prevent accidental secret leakage by scanning staged changes for sensitive data. This skill acts as a pre-commit gate, blocking commits containing credentials and PII using regex and entropy matching.

Can I use this to scan staged diffs for internal IPs and PII?

Yes, you can scan staged diffs for internal IPs and PII. The skill performs an AI review on staged changes to detect sensitive information, including credentials and configuration files, without manual inspection.

Does this secret scanning tool enforce security policies for code review?

Yes, this secret scanning tool enforces security policies during code review. It ensures strict adherence to organizational security guidelines by blocking commits that contain known secrets or sensitive configuration files.

What is the best way to check for credentials in staged git changes?

The best way to check for credentials in staged git changes is to run `git diff --cached` and use this skill. It scans the staged diff for potential leaks like credentials and internal IPs before the commit is finalized.

Will git leak prevention block commits with known secrets?

Yes, git leak prevention will block commits with known secrets. It functions as a pre-commit gate that identifies sensitive information through regex and entropy matching, stopping the commit before it reaches your repository.