# Repo Separation For Sensitive Data

> Architecture pattern for splitting confidential data and reusable algorithms across repos

- Skill: `vamseeachanta/repo-separation-for-sensitive-data` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vamseeachanta/repo-separation-for-sensitive-data`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vamseeachanta/repo-separation-for-sensitive-data/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vamseeachanta (https://skillmd.com/u/vamseeachanta)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vamseeachanta/repo-separation-for-sensitive-data

---


# Repo Separation for Sensitive Data & Algorithms

When building personal finance or sensitive-data projects, separate confidential inputs (transactions, positions, account data) into a private personal repo while algorithms/analysis code lives in a shared/public repo. This lets you version control logic independently, share code without exposing data, and keep sensitive CSVs/configs in `.gitignore`. Example: `achantas-data` (private, holds transactions & positions) + `assethold` (shared, holds analysis algorithms). Reference cross-repo issues to track dependencies.