← ClaudeAtlas

repo-showcaselisted

Turn a basic GitHub repository into a publish-ready showcase. Interviews the user (purpose, audience, goal, length, mascot, links), audits secrets and personal data in the files and the whole git history, removes AI co-authorship mentions, audits the file structure, then builds a short, very visual README (custom animated SVG banner, screenshots, live counters) and checks the GitHub rendering before pushing. Use when the user wants a repository to look professional, to highlight their profile, to prepare it for going public, or to check it holds no personal data.
titouannwtt/claude-tools · ★ 1 · AI & Automation · score 74
Install: claude install-skill titouannwtt/claude-tools
# repo-showcase Goal: a visitor understands the project in five seconds, from the visuals alone, and nothing private leaks. Short and visual beats long: if it is long nobody reads it; if it is short and visual, people at least look at the images, and if the images are clear the project is understood at a glance. Script: `S=~/.claude/skills/repo-showcase/scripts/showcase.py` (`python3 $S <command>`, JSON on stdout). Run `python3 $S doctor` once per machine: it says what is possible (history rewrite, screenshots, faces, demo). ## Hard rules - Never change a repository's visibility. For a private repository, the last message says: going public is the user's last step (`ready` prints the command for them). - Never print or store a raw secret: talk about findings with their preview and fingerprint only. - Normal push and `gh repo edit` (description, topics, homepage) only after the user validated the preview. - History rewrite and force push: only after an explicit yes, asked separately each time. Never delete or move a file without agreement. - Remove every AI co-authorship mention (commits, files, pull requests, releases). A project that is *about* AI keeps its product mentions. - Commits: `git config user.email` must be a noreply address; no AI attribution in messages. - No hard-coded number that changes often in a visual or the README, unless it is live (badge), synced (`counts`), or a dated measurement. ## Workflow 1. **Facts** (no questions yet): `inventory <re