github-release-guide
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.
npx skills add kyungseo/skillstead --skill github-release-guide --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-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 infe
- Package map
- Supported contract
- Establish the target
- Choose the mode
- Assess
- Guided
- Apply evidence and decision rules
- Handle failure safely
- Communicate for non-experts
- Completion rule
What does the github-release-guide skill do?
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.
How do I install it?
Run `npx skills add kyungseo/skillstead --skill github-release-guide --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 kyungseo/skillstead, a repository with 69 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.