strip-claude-from-repo-for-publiclisted

# Strip Claude For Public ## Overview Removing Claude footprint before a public flip is **two separate problems**: file artifacts in the tree, and metadata in git history. A repo can have a spotless working tree and still leak everything via Co-Authored-By trailers, Claude-named commit subjects, branches, and merge commits — and the `public-readiness-audit` agent does **not** flag commit metadata. Decide history handling before the flip, because a non-squashed history exposes all of it. ## When to Use - Flipping a Claude-built repo from private to public - Generating/publishing a public mirror of a private repo - Any "make this repo shareable" task where Claude authored commits ## Steps 1. **Tree refs:** `git grep -i claude` for files, README bullets, CLAUDE.md, installer scripts, `docs/superpowers/`, Claude-only secrets. 2. **Map coupling before deleting.** Removing a Claude-only secret or script may orphan a generic framework. Keep the generic framework; neutralise only the Claude-coupled variable. 3. **Confirm test suites don't enumerate deleted scripts by name** (a globbed bootstrap is safe; a hardcoded list breaks). 4. **History:** `git log --format='%an %ae %s' | grep -i claude` and check trailers, branch names, and merge-commit subjects. **Scope the audit and any rewrite to `git log main`** (what actually ships), NOT `git log --all` — `--all` over-reports unreachable feature-branch tips that never go public, causing false-positive panic. R