github-release-guide

Solid

Assess and guide safer github.com repository releases. Use when an existing private GitHub repository becomes public for the first time, or whenever an already-public GitHub repository publishes a new version, and the user needs readiness checks, release-surface decisions, explicit mutation approvals, release notes, settings checks, or post-release verification. Supports read-only Assess and approval-gated Guided modes. Do not use for repository bootstrap, package registries, signing, cloud deployment, security audits, GitHub Enterprise, other providers, force-push, or history rewrite.

Code & Development 66 stars 12 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# github-release-guide Guide a GitHub release without taking release authority away from the user. Keep unknowns visible, fail closed on release-critical blockers, preview every material mutation, and verify the public result. ## Package map Load references progressively, but never skip a required load: | File | Load rule | | --- | --- | | `references/assessment.md` | Always load before classifying readiness or proposing a mutation | | `references/first-public.md` | Load for an existing private github.com repository's first public release | | `references/version-release.md` | Load for every new version released from an already-public github.com repository | If a selected profile reference cannot be loaded, continue only with a partial read-only Assess and mark the missing profile rules as unknown. **Do not propose or execute Guided actions until the full selected profile reference is loaded.** ## Supported contract Support only: - Mode: `Assess` or `Guided` - Release profile: `first-public` or `version-release` - Provider: `github.com` - Claim-audit profile: `public-baseline` by default, or `internal-strict` only when the user or a repository policy explicitly selects it Never infer `internal-strict` from a repository name, owner, visibility, organization, or local path. Never treat the current working directory as the release target without confirming repository identity. If the user asks for an unsupported release type, stop at a read-only boundary assessment an...

Details

Author
kyungseo
Repository
kyungseo/skillstead
Created
2 weeks ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category