skills.rest
ShadowAUS
ShadowAUSCOMMUNITY
Explore all skills by this author →
GitHub

github-release

Automates GitHub releases with safety checks, validation, tagging, and publishing via gh CLI.

Updated Aug 23, 2026
Search Tags:#automation#github#release#tagging#license-check#secrets-scan
One-click install
npx skills add https://github.com/ShadowAUS/chez-king-portal --skill github-release-shadowaus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-release
Source: https://github.com/ShadowAUS/chez-king-portal/tree/main/.tessl/tiles/jezweb/claude-skills/plugins/dev-tools/skills/github-release
Command: npx skills add https://github.com/ShadowAUS/chez-king-portal --skill github-release-shadowaus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the GitHub release process by performing safety checks, validating licensing and documentation, and tagging and publishing releases via the gh CLI.

Core Features & Use Cases

  • Automated safety checks (secrets scan, artifact cleanup) before release
  • License and README validation to ensure repository hygiene
  • Version tagging and GitHub release publishing via gh
  • Use Case: teams needing repeatable, compliant release workflows for open-source projects

Quick Start

Run the release workflow against your repository to sanitize, tag, and publish the release.

Frequently Asked Questions about github-release

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

FAQPage Schema
How do I automate GitHub release publishing with safety checks?▼

Automate GitHub release publishing by running a workflow that performs secrets scanning, artifact cleanup, license validation, and automated tagging via the gh CLI. This ensures releases are safely prepared and published.

What is the process for tagging and publishing a GitHub release safely?▼

Tagging and publishing a GitHub release safely requires validating repository hygiene like LICENSE and README files, scanning for secrets with gitleaks, and using the gh CLI to create the final release.

Do I need gitleaks and gh CLI configured to automate repository releases?▼

Yes, automating repository releases requires the gh CLI for publishing and gitleaks for secrets scanning. You also need a Git repository with a remote configured and valid repository setup.

How does secrets scanning work during the GitHub release workflow?▼

Secrets scanning during the GitHub release workflow uses gitleaks to scan the repository before tagging. This safety check prevents sensitive information from being published in the automated release.

What happens if my repository is missing a LICENSE or README during release automation?▼

Release automation performs license and README validation to ensure repository hygiene. If these files are missing, the workflow determines the repository lacks release readiness and halts the publishing process.

Can I use this automated release workflow for open-source project compliance?▼

Yes, teams needing repeatable, compliant release workflows for open-source projects can use this automation to enforce safety checks, validate documentation, and publish releases consistently.

Related Skills

Explore More Software Engineering Skills→
Mathews-TomMathews-Tom
310

repo-sentinel

Audit Git repositories for security and public-release readiness across attack surfaces.

Community
Advanced
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
1479089714790897
7

github

Manage GitHub issues, pull requests, and CI/CD workflows via gh CLI.

Community
Intermediate
mistakenotmistakenot

release

Tag commits with semantic versions and publish release assets via GitHub Releases.

Community
Advanced