Detect and audit sensitive data and credentials in git-tracked files.
npx skills add https://github.com/helderberto/dotfiles --skill safe-repo
Please help me install this Agent Skill. Skill: safe-repo Source: https://github.com/helderberto/dotfiles/tree/main/claude/.claude/skills/safe-repo Command: npx skills add https://github.com/helderberto/dotfiles --skill safe-repo
This Skill detects and audits sensitive data in a repository to prevent credentials leakage and accidental exposure.
Run the safe-repo skill against your repository to perform a security audit for secrets and sensitive data.
High-intent search queries and answers about installing and using this skill.
To scan a git repository for leaked secrets, you can run an audit tool that searches git-tracked files using git ls-files. This process detects common credential patterns and sensitive data without exposing the actual secret values.
Secret detection in git history involves scanning tracked files and commit logs to find accidentally committed credentials. You need it during pre-release checks, security audits, or CI pipeline integration to prevent credentials leakage.
Yes, you can integrate this secret scanning approach directly into your CI pipeline. It provides CI-ready checks designed to catch secrets in tracked files and history before they are committed or released, preventing accidental exposure.
No, the repository audit does not scan untracked files. It specifically searches only git-tracked files using git ls-files to detect .env files, credential patterns, and keys in history, ensuring focused and compliant security checks.
The best way to prevent .env files from being committed is running pre-release security audits that detect credential files and common secret patterns. This identifies sensitive data in tracked files before it enters your repository history.
No, the security audit will not expose your actual secret values. It detects sensitive data and credentials across the repository, reporting findings securely without printing the matched values to prevent further accidental exposure.
tellbomInitialize a Git repository with an initial commit in a project directory.
mpauloskyBlock commits containing detected secrets and forbid reading live .env files.
voidrotConfigure SAST tools like Semgrep, CodeQL, and SonarQube for CI/CD pipelines.
arbazkhan971Detect exposed secrets and rotate credentials into secret managers.
