Detect and flag personal data and secret tokens in code repositories.
npx skills add https://github.com/0xjitsu/jitsu-skills --skill pii-sweep
Please help me install this Agent Skill. Skill: pii-sweep Source: https://github.com/0xjitsu/jitsu-skills/tree/main/skills/pii-sweep Command: npx skills add https://github.com/0xjitsu/jitsu-skills --skill pii-sweep
Detect and remediate personally identifiable information (PII), credentials, and internal references scattered across a repository before it is published or shared, reducing the risk of accidental data leaks or credential exposure.
Ask the skill to run a full PII sweep of the current repository and guide you through reviewing and replacing any findings.
High-intent search queries and answers about installing and using this skill.
To scan a code repository for secrets and PII, run a regex-based sweep across source files, documentation, and configuration files to detect emails, phone numbers, API keys, and internal URLs before publication. It groups findings by category for safe review and non-destructive replacement.
The best way to remove API keys and personal data is to use a non-destructive replacement workflow that requires explicit user classification of findings as true or false positives. Confirmed secrets are moved to .env files, while personal data is replaced with standardized placeholders.
Regex pattern matching detects credentials by applying targeted regular expressions to identify specific data structures like API keys, spreadsheet IDs, and physical addresses across your source code and config files. It then presents contextual evidence for each flagged item.
The PII sweep workflow does not automatically rewrite git history to remove exposed tokens. It warns about potential leaks in git history and recommends safe history-rewrite tools, but it deliberately avoids performing destructive operations automatically to protect your repository.
You can use this to prepare a private repo for a security audit by scanning README files, source code, and configuration to ensure no live keys or personal data remain. It skips binaries, lockfiles, and vendor directories, then re-runs verification passes to achieve zero findings.
When scanning a repository for sensitive internal URLs, the workflow automatically skips .git, node_modules, vendor directories, binaries, and lockfiles. This ensures the sweep only targets relevant source files, documentation, and configuration files without wasting time on dependencies.
AstrumonCreate standardized Git commits with validated type: description messages.
ealvar3zRemove a specified file from entire Git repository history using git-filter-repo.
CodySwannGTValidate Expo environment variables with Zod schemas at build and runtime.
DuqueOMDetect security flaws in code, configurations, and containers before deployment.
