What problem does it solve? It stops real personal data — IBANs, names, salaries, rents, bank exports — from leaking into a public git repository through test fixtures, CHANGELOG entries, screenshots, or pasted installation output, where git history makes removal nearly impossible. ## Core Features & Use Cases - Fixture fabrication rules: Defines how to build synthetic bank CSV fixtures (N26, MyInvestor) that still exercise parser behavior like autodetection, encoding, dedup, and transfer matching without copying any real row. - Documentation and CHANGELOG hygiene: Requires invented but arithmetically coherent example numbers and screenshots sourced only from a seeded demo installation. - Leak response procedure: Provides a step-by-step git history rewrite workflow using git filter-repo, verification across all commits, and credential rotation guidance. - Use Case: Before adding a new bank CSV fixture or writing a CHANGELOG entry with before/after numbers, load this Skill to verify the data is fabricated and passes the blocking scan-sensitive.sh CI gate. ## Quick Start Ask the assistant to review the new bank CSV fixture you are about to commit and confirm it contains no real personal data before pushing.