This automates the paranoid checklist you should run before making a repo public. It's a two-phase workflow: first it scans for secrets with gitleaks, hunts down personal artifacts like SESSION.md or planning directories, and validates your LICENSE and README exist. Then it handles the actual release mechanics with git tags and gh CLI. The blocker system is smart, it won't let you proceed if secrets are detected but treats build failures as warnings. Honestly most useful for solo devs or small teams who don't have release automation set up yet and keep almost pushing API keys to public repos.
npx skills add https://github.com/jezweb/claude-skills --skill github-release