Github Release

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.

skills.sh installs: 1.3K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jezweb/claude-skills --skill github-release --agent claude-code

Installs into .claude/skills of the current project.

Files

GitHub Release

Sanitize and release projects to GitHub. Two-phase workflow: safety checks first, then tag and publish.

Prerequisites

gh CLI installed and authenticated (gh auth status)
gitleaks installed for secrets scanning (brew install gitleaks or download from GitHub)
Git repository with a remote configured

Workflow

Phase 1: Sanitize

Run these checks before any public release. Stop on blockers.

1. Scan for Secrets (BLOCKER)

gitleaks detect --no-git --source=. --verbose

If secrets found: STOP. Remove secrets, move to environment variables. Check git history with git log -S "secret_value" — if in history, use BFG Repo-Cleaner.

If gitleaks not installed, do manual checks:

# Check for .env files
find . -name ".env*" -not -path "*/node_modules/*"

# Check config files for hardcoded secrets
grep -ri "api_key\|token\|secret\|password" wrangler.toml wrangler.jsonc .dev.vars 2>/dev/null