proprietary-leak-scan

Proprietary Leak Scan

Overview

CTObot is a public, MIT-licensed repository. The public files must stay generic and tool-agnostic. Company-specific material — our org, customers, employees, infrastructure, money, and anything covered by GLBA (NPI/PII) — must live only in the git-ignored company_proprietary/ folder, never in AGENTS.md, SOUL.md, docs/, README.md, or skills/.

This skill detects "slippage": content that has leaked into the public files. It works by reading and reasoning, not by matching keywords. A regex finds yourcompany@, but it misses the things that actually leak: a real customer described without being named, an internal incident retold as an "example", a specific architecture or vendor stack, headcount or budget figures phrased in prose, a process that only makes sense inside our company. You (the agent) read the changes and judge whether each piece of content could only have come from our company — that is the test.

Run it before every commit. It is defense in depth on top of .gitignore, and a complement to reading your own diff, not a replacement for it.

When to Use

Use when:

• you are about to commit or push to the public repo
• you just adapted a generic framework with real, company-specific detail
• you pasted notes, transcripts, or session learnings into a skill references/ file
• you are reviewing a contribution / PR before merge

Do not use for code-bug or doc-quality review (out of scope), or to scan company_proprietary/ itself (that content is supposed to live there).

What to review

Prefer the diff — it is where new leakage enters:

git diff --cached            # staged changes (the pre-commit gate)
git diff HEAD                # all uncommitted changes
git diff <base>...HEAD       # everything on this branch vs. the base

If there is no git history, the change set is unclear, or you want a full audit, read all files in the public tree instead. Either way, exclude company_proprietary/, .git/, node_modules/, and this skill's own folder.