Data Leakage Prevention

Use this skill for submission-time security checks and general file compliance reviews. Combine semantic review with deterministic tooling, and make the audit boundary explicit before any scan starts.

Core Rules

1. Declare the audit boundary first. State the scope type and the resolved files before scanning.
2. Collect environment context early. Check whether the target is git-backed, whether .gitleaks.toml or similar policy files exist, whether .pre-commit-config.yaml exists, and whether local text-extraction tools are available for binary documents.
3. Respect repository rules before running detectors. If .gitleaks.toml or similar config exists, honor its ignore rules and use its custom rules as review constraints when possible.
4. Choose scan depth from the change summary. Do not default to full semantic review for generated, third-party, or oversized changes.
5. Report precise findings and keep likely false positives separate.

Boundary And Context

Supported scope types:

• Git: staged, changed, commit <hash>, pr <id>
• Filesystem: entire repo, directory, specific file