github-release
Prepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.
npx skills add jezweb/claude-skills --skill github-release --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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) ```bash 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: ```bash # 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 ``` #### 2. Remove Personal Artifacts Check for and remove session/planning files that shouldn't be published: - `SESSION.md` — session state - `planning/`, `screenshots/` — working directories - `test-*.ts`, `test-*.js` — local test files Either de
- Prerequisites
- Workflow
- Phase 1: Sanitize
- Phase 2: Release
- Reference Files
gitleaks detect --no-git --source=. --verbose 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 ls LICENSE LICENSE.md LICENSE.txt 2>/dev/null grep -i "## Install\|## Usage\|## License" README.md grep -E "node_modules|\.env|dist/|\.dev\.vars" .gitignore npm run build 2>&1 npm audit --audit-level=high
What does the github-release skill do?
Prepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.
How do I install it?
Run `npx skills add jezweb/claude-skills --skill github-release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jezweb/claude-skills, a repository with 954 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.