github-release

Sanitize repositories and publish versioned GitHub releases via gh CLI.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill github-release-scsm-unrestrict
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-release
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/github-release
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill github-release-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Publishing a project to GitHub risks leaking secrets, personal artifacts, or missing license files, and the tag-and-release process involves many error-prone manual steps. This Skill enforces a two-phase workflow that sanitizes the repository first, then creates version tags and publishes the release. ## Core Features & Use Cases - Pre-release Sanitization: Scans for secrets with gitleaks, removes personal artifacts like SESSION.md and planning directories, and validates LICENSE, README, and .gitignore before anything goes public. - Tag and Release Automation: Determines the version from package.json, checks for tag conflicts, pushes branch and tags, and creates the GitHub release with generated notes via the gh CLI. - Use Case: Before open-sourcing a side project, run the workflow to catch a hardcoded API token in wrangler.toml, add a missing MIT license, then publish v1.0.0 with auto-generated release notes. ## Quick Start Prepare this repository for public release and publish it as v1.0.0 on GitHub.

Frequently Asked Questions about github-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub release from the command line?▼

Use gh release create with a version tag, title, and notes, such as gh release create v1.0.0 --title "Release v1.0.0" --notes "...". Add --prerelease for beta versions or --draft to save without publishing.

How to scan a repository for secrets before publishing?▼

Run gitleaks detect --no-git --source=. --verbose to scan working files for API keys, tokens, and private keys. If secrets appear in git history, use git log -S to locate them and BFG Repo-Cleaner to remove them.

What should I check before open sourcing a project?▼

Verify no secrets exist in files or git history, a LICENSE file exists, the README has Install, Usage, and License sections, and .gitignore covers node_modules and .env. Also remove personal artifacts like session notes and local test files.

What if the git tag already exists when releasing?▼

Delete the local tag with git tag -d v1.0.0 and recreate it. If the tag was already pushed to the remote, deleting it remotely requires git push origin :refs/tags/v1.0.0, which should be confirmed with the user first.

Does this release workflow work without gitleaks installed?▼

Yes, the workflow includes manual fallback checks using find and grep to locate .env files and hardcoded secrets in config files like wrangler.toml. However, gitleaks provides more thorough pattern-based detection.