privacy

To scan a Git repository for sensitive data before committing, run a privacy review on staged changes and recently modified files. This process flags personal identifiers and client information, recommending moving risky content to a .private/ directory to prevent public data exposure.

Preventing accidental exposure of personal data in public GitHub repos involves scanning staged files for sensitive information before a commit. A privacy-focused code review identifies personal identifiers and internal notes, recommending quarantine to a .private/ folder for safety.

This privacy review tool checks both staged changes and recently modified docs or code. It scans these files for personal identifiers, sensitive business information, and internal notes that could be harmful if publicly visible on GitHub.

The sensitive data flagging mechanism works by applying guidelines for judgement rather than simple pattern matching during code reviews. It evaluates staged content for privacy risks like client names or personal data and provides a clear remediation workflow to move items to .private/.

Yes, you can use this skill to quarantine internal notes and client names in your codebase. It identifies sensitive business information during pre-commit reviews and recommends moving flagged items to a .private/ directory to maintain privacy.

You should run a privacy scan on your repository content before merging docs updates or committing staged changes. Running a review at these points catches accidental exposure of personal identifiers or sensitive business information before it leaves your repo.