secret-exposure-prevention

Identify secret leakage patterns and validate exclusion rules across git history and CI pipelines.

Updated Apr 11, 2026

Search Tags:#security #compliance #prevention #scanning #git-history #secret-management #secret-exposure

Ready to run

npx skills add https://github.com/chf3198/devenv-ops --skill secret-exposure-prevention

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secret-exposure-prevention
Source: https://github.com/chf3198/devenv-ops/tree/main/skills/secret-exposure-prevention
Command: npx skills add https://github.com/chf3198/devenv-ops --skill secret-exposure-prevention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent secret leakage across git history, package artifacts, logs, and docs. Use when editing workflows, packaging configuration, environment files, or release automation.

Core Features & Use Cases

Identify secret-bearing file patterns in repos and tooling context.
Verify exclusion rules (.vscodeignore, .npmignore, artifact manifests) and prevention controls (pre-commit, CI scanning, secret scanning backstops).
Propose targeted guardrails to enforce placeholder usage and minimize risk in workflows and releases.
Use Case: When refactoring authentication flows, run this to ensure secrets are redacted and guarded.

Quick Start

Scan your repository to identify secret exposure risks and apply targeted guardrails.

Frequently Asked Questions about secret-exposure-prevention

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

FAQPage Schema

How do I scan my git history for secret exposure?▼

To scan git history for secret exposure, identify secret-bearing file patterns across repository changes and tooling context, then validate exclusion rules like .vscodeignore and .npmignore to prevent leakage. This process checks historical commits and current changes for sensitive data.

What is the best way to prevent secrets from leaking in CI pipelines?▼

Preventing secret leakage in CI pipelines involves enforcing scanning controls such as pre-commit hooks, CI scanning, and secret scanning backstops. This ensures secrets are redacted and guarded during release automation and packaging workflows.

How do I verify .npmignore and .vscodeignore rules are blocking secret-bearing files?▼

Verify exclusion rules by validating .npmignore and .vscodeignore configurations against artifact manifests to ensure secret-bearing file patterns are excluded. This targets environment files and packaging workflows to minimize secret exposure risk.

How do I redact secrets when refactoring authentication flows?▼

When refactoring authentication flows, redact secrets by enforcing placeholder usage in examples and applying targeted guardrails. This mitigates secret leakage across documentation, logs, and environment files during the refactoring process.

Does secret exposure prevention work with local development environments?▼

Yes, secret exposure prevention applies to local development and CI pipelines. It identifies risks in environment files and tooling context, providing guidance for remediation and guardrails across repository changes and release automation.