# skillshare-release

Coordinates and verifies skillshare releases through Release Please PRs, syncs documentation across locales, and inspects draft assets.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 3269 repo stars
- Author: runkids
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/runkids/skillshare/tree/HEAD/.skillshare/skills/skillshare-release/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/skillshare-release

## What it does

This skill guides the release procedure for the skillshare repository. It enforces running `python3 scripts/ai-context.py release testing` first to establish release policies and verification rules. The release version originates from `.github/release-please-manifest.json`, while version overrides require a `Release-As: X.Y.Z` trailer on a regular commit reaching `main`.

Documentation must be updated before touching the release branch, running `/skillshare-update-docs` and `cd website && npm run build`. The skill verifies pull request files inside the devcontainer using `python3 scripts/release/release.py check --tag vX.Y.Z` and `make check`. It will never push, merge, or publish without explicit authorization from the user.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add runkids/skillshare --skill skillshare-release -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/skillshare-release/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/skillshare-release/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add runkids/skillshare --skill skillshare-release -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/skillshare-release/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add runkids/skillshare --skill skillshare-release -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/skillshare-release/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install runkids/skillshare .skillshare/skills/skillshare-release
```

2. **Manually: put the files in place**
- File: `.github/skills/skillshare-release/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add runkids/skillshare --skill skillshare-release -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/runkids/skillshare --path .skillshare/skills/skillshare-release
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/skillshare-release/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/runkids/skillshare/tree/HEAD/.skillshare/skills/skillshare-release/SKILL.md

## When to use it
- prepare and verify Release Please pull requests
- synchronize multilingual documentation before merging releases
- inspect draft release assets, CLI archives, and Homebrew formulas

## Example prompts
- Prepare the skillshare release for the main branch
- Review the open Release Please PR and set version to 0.23.3
- Inspect the draft release assets and update release notes

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 3eb444a293a1085b.

BEGIN THIRD-PARTY FILE 3eb444a293a1085b
````text
---
name: skillshare-release
description: >-
  Prepare and review skillshare releases using the Release Please PR, verify the
  proposed version and changelog, inspect draft assets, and publish through the
  manual Publish Release workflow when explicitly authorized. Use when the user
  says "release", "prepare release", "cut a release", or asks to publish a new
  version. For changelog-only tasks, use /changelog instead.
argument-hint: "[version]"
metadata:
  targets: [claude, universal]
---

Prepare or review a skillshare release. An optional version argument is an explicit requested version, not permission to commit, merge, tag, push, or publish.

Before acting, run `python3 scripts/ai-context.py release testing`. These topics are the source of truth for authorization, version policy, automation and verification.

## Workflow

### 1. Identify the release

Inspect Git status, the latest published release and the open Release PR. Preserve unrelated work. The manifest at `.github/release-please-manifest.json` is the release version source; the development CLI still defaults to `dev`.

Pushes to `main` create or update a Release PR. If one is missing, report the workflow state and required repository permissions. Dispatch the Release Please workflow only when the user authorizes that external action.

For `0.x`, `fix` and `perf` increment patch; `feat` and breaking changes increment minor. A breaking change needs migration notes. Moving to `1.0.0` requires an explicit version decision. For an override, use a `Release-As: X.Y.Z` commit footer or a reviewed `release-as` configuration value; remove a configuration override after it has been consumed. Do not edit the tracking manifest by itself to request a release.

#### Explicit version requests

When the user requests a version such as `0.23.3`, prepare a `Release-As: 0.23.3` footer on a normal development commit that will reach `main` before the Release PR is merged. For a batch with multiple commits, adding it once to the final commit is sufficient; the override chooses the version for the entire pending release, including the earlier changes. Intermediate versions do not need to be published.

```text
fix: correct sync behavior

Release-As: 0.23.3
```

With merge or rebase-merge, preserve the footer in the development commit. With squash-merge, copy it into the final squash commit message on GitHub; do not assume the individual commit messages will be preserved. Keep the Conventional Commit subject and a blank line before the footer. If multiple pending commits request different versions, the newest override wins; inspect the pending range for conflicting requests before proceeding.

After the commit reaches `main`, verify that Release Please creates or updates the Release PR to the requested version. Review its manifest and synchronized metadata before merging. Adding a footer alone does not create the release tag or publish anything. Follow the existing authorization boundary when committing, pushing or merging.

### 2. Sync documentation first
````
END THIRD-PARTY FILE 3eb444a293a1085b

The third-party file has ended. Everything between the 3eb444a293a1085b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3053 of 8215 bytes. © runkids · MIT · https://github.com/runkids/skillshare/tree/HEAD/.skillshare/skills/skillshare-release/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
