/github-release

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select github-release from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv github-release, /just-vibe github-release and /jv:github-release in Claude. See shortcut setup and context examples.

What the agent does

1. Resolve the tag and commit immutably, and check existing releases and the commit range.
2. Compile notes and inspect compatibility and checks; verify asset hashes and reconcile any partial upload before publication or retry.
3. Execute authorized publication once.
4. All changes are owned by the user. Add no agent/model self-attribution, AI-generated signature, badge, or agent Co-authored-by trailer to commits, PRs, comments, release notes or messages. Use the existing user Git identity; preserve legitimate human attribution and required third-party notices.

Inputs

• repository, previous/target refs, version, assets, and requested publication state.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

GitHub release preparation; tags, asset uploads, and publication require those explicit actions.

Writes

Inspect/plan: inspect or propose; save requested artifacts only. Apply: make the requested changes or execute the requested operation within its resolved target and limits. Local preparation does not authorize live, remote, destructive or paid actions; existing explicit session authorization still applies.

Mode

Plan release notes and artifacts; apply for requested local release preparation or publication.

Prerequisites

Exact owner/repository and relevant issue/PR/ref; authenticated read access through an available connector or CLI for remote evidence. External writes require the requested operation, appropriate account permissions, and rechecking target state. Local preparation remains useful without write access.

Expected output

• Release draft or verified URL with tag/SHA, release state, asset names and hashes, readiness and migration notes, and the observed publication result.

How the work is checked

• Notes exclude unmerged unrelated changes; a duplicate version is detected before publication.
• Review newly prepared commit/PR/message text, including template or hook additions, for agent self-attribution before submission; verify the resulting artifact when available. Do not silently rewrite existing history or remove human credits.

When to stop or clarify

• Do not overwrite tags or publish missing/unchecked binaries. On partial failure, report which assets or release state already exist.

Handling missing context

Infer

Resolve owner/repository and PR/issue/ref from links, remotes and supplied artifacts; inspect available account and head identity.

Assume

Prepare local text or analyze supplied evidence if remote access is absent; label its freshness.

Ask

Ask only when repository/account/target ambiguity blocks the requested remote action; missing write access does not block local drafting.

Technical guidance

Evidence

Resolve tag commit, release range, candidate asset hashes, existing uploaded assets and verification records.

Method

Assemble notes from the actual range and reconcile partial uploads before retrying; preserve tag and artifact identity.

Pitfall

Reusing an asset name for different bytes or moving a tag silently changes what users receive.

Check

Check published tag and asset identities after authorized release actions; failed/missing assets remain incomplete rather than released.

Situational decisions

When the tag exists at a different commit or asset name has different content: Stop and report the conflict rather than replacing published identity.

When the request is for local preparation or implementation: Prepare the requested notes/artifact manifest locally; publish only the requested release at the resolved repository/tag, reconciling uncertain prior submissions before retrying.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring