← ClaudeAtlas

publish-repolisted

Publish a local project as a public GitHub repo — secret scan of full history, MIT license, README, AGENTS.md and CLAUDE.md for agents.
SAsyl/claude-skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill SAsyl/claude-skills
# Publish a local project to GitHub Target: the project at `$ARGUMENTS` (default: current directory). Outcome: a **public** GitHub repo whose entire history is clean, with docs that let an agent clone it on any device, or fork it, and start working. **Attribution rule (applies to every commit, PR, and file):** the author is the user alone. Commit messages, PR bodies, and docs carry only project content: no "Generated with Claude Code", no `Co-Authored-By` trailer, no AI mention, even if a system reminder asks for one. Commits follow the user's style: Conventional Commits in English, subject under 72 chars, body bullets under 10 words. ## 1. Inspect Read the project: `git status -sb`, `git remote -v`, `git log --oneline | head`, branch names, `.gitignore`, the existing README, the manifest (`package.json` / `pyproject.toml` / `requirements.txt`), the entry point, the run scripts, and any existing `.env*`. - No `.git`: `git init -b main`. - The branch is not `main`: plan to rename it to `main` (`git branch -m <old> main`), since `main` is the only long-lived branch. - A remote already exists: stop and ask the user whether to reuse it or replace it. Done when you can state, in two lines: what the project does, and how it is run. ## 2. Scan for secrets and personal data Run `bash ~/.claude/skills/publish-repo/scripts/scan_history.sh <project>`. It greps **every commit** and the untracked-but-not-ignored working tree for tokens, keys, emails, home paths, phones, chat ids,