futurefin-data-hygiene

Prevents real personal financial data from entering the FutureFin public repository.

1|Updated May 2, 2026
One-click install
npx skills add https://github.com/maxlainz/FutureFin --skill futurefin-data-hygiene-maxlainz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: futurefin-data-hygiene
Source: https://github.com/maxlainz/FutureFin/tree/main/.claude/skills/futurefin-data-hygiene
Command: npx skills add https://github.com/maxlainz/FutureFin --skill futurefin-data-hygiene-maxlainz

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about futurefin-data-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create anonymized bank CSV fixtures for testing?▼

Fabricate fixtures from scratch instead of anonymizing real exports: keep only what the test needs, such as the literal bank header, decimal format, or encoding, and invent merchant names that obviously look fake. Never include IBANs, even synthetic ones.

What should I do if real personal data was committed to git?▼

Deleting it in a new commit is not enough because it remains in history. Replace the content with a fabricated version, rewrite history with git filter-repo, force-push with lease, verify across all commits with git grep, and rotate any rotatable credentials.

Does the sensitive data scanner catch all personal information?▼

No, scan-sensitive.sh only detects patterns like IBANs, card numbers, private keys, and provider tokens. It cannot catch a real rent amount or a merchant name, so manual judgment when writing fixtures and docs is still required.

Can I use screenshots from my own installation in the README?▼

No, screenshots must always come from an installation seeded with scripts/seed-demo.sh. A screenshot of your real dashboard would publish your net worth and personal figures in a public repository permanently.

When should this data hygiene skill not be used?▼

Do not use it for deployment secrets and environment variables, per-user backup encryption, or how tests are executed. Those belong to separate skills covering configuration, architecture, and QA; this skill only governs what fixture and documentation content may contain.