github-release
Installation
Summary
Sanitize code for secrets and artifacts, then create and publish GitHub releases with version tags.
- Two-phase workflow: Phase 1 runs blocking checks (secrets scan with gitleaks, LICENSE/README validation, personal artifact removal) and stops on failures; Phase 2 creates version tags and publishes via gh CLI
- Requires
ghCLI authenticated,gitleaksinstalled, and a Git repository with a remote configured - Includes non-blocking checks for build success and dependency vulnerabilities, plus automatic sanitization commits if changes are made
- Displays commit history between the last tag and HEAD before release, and reports the release URL and next steps upon completion
SKILL.md
GitHub Release
Sanitize and release projects to GitHub. Two-phase workflow: safety checks first, then tag and publish.
Prerequisites
ghCLI installed and authenticated (gh auth status)gitleaksinstalled for secrets scanning (brew install gitleaksor 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)
Related skills
More from jezweb/claude-skills
tailwind-v4-shadcn
|
2.7Ktanstack-query
|
2.5Kshadcn-ui
Install and configure shadcn/ui components for React projects. Guides component selection, installation order, dependency management, customisation with semantic tokens, and common UI recipes (forms, data tables, navigation, modals). Use after tailwind-theme-builder has set up the theme infrastructure, when adding components, building forms, creating data tables, or setting up navigation.
2.5Ktailwind-theme-builder
>
2.2Kfastapi
|
2.0Kcolor-palette
>
1.9K