docs: add privacy rule to CLAUDE.md (never leak private setup)#42
Merged
Conversation
Codifies the standing instruction: no personal paths, real hub config, hook names, secrets, or other-project names in any tracked file. The repo ships only the product + public tooling; private working docs stay in gitignored research/ or .scratch/. Prevents a repeat of the hub paths that leaked into the benchmarks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Aggiunge al
CLAUDE.mddi progetto una sezione Privacy che codifica la regola: mai mettere nel repo pubblico path personali, config reale dell'hub, nomi degli hook, segreti o nomi di altri progetti. Chiarisce che il repo contiene solo il prodotto (plugin/skill/commands/hooks/scripts) + tooling pubblico + benchmark con dati sintetici, e che i doc privati (idee/roadmap/note) restano fuori da git inresearch/o.scratch/.Nasce dal leak appena ripulito (PR #41): serve la regola scritta per non ripeterlo.
🤖 Generated with Claude Code