Suede Launch Packaging
JasonColapietro/suede-creator-skills
Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.
A skill your agent uses when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.
Install Release Prep
$ npx skills add johnhuang316/code-index-mcp --skill release-prep -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install johnhuang316/code-index-mcp release-prep --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/johnhuang316/code-index-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-prep .claude/skills/release-prep && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-prep" agent skill from https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prep into .claude/skills/release-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-prep", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prepType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add johnhuang316/code-index-mcp --skill release-prep -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install johnhuang316/code-index-mcp release-prep --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johnhuang316/code-index-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-prep .agents/skills/release-prep && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-prep" agent skill from https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prep into .agents/skills/release-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-prep", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add johnhuang316/code-index-mcp --skill release-prep -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install johnhuang316/code-index-mcp release-prep --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johnhuang316/code-index-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-prep .cursor/skills/release-prep && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-prep" agent skill from https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prep into .cursor/skills/release-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-prep", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/johnhuang316/code-index-mcp.git --path .agents/skills/release-prep--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add johnhuang316/code-index-mcp --skill release-prep -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install johnhuang316/code-index-mcp release-prep --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johnhuang316/code-index-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-prep .gemini/skills/release-prep && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-prep" agent skill from https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prep into .gemini/skills/release-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-prep", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install johnhuang316/code-index-mcp release-prepInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add johnhuang316/code-index-mcp --skill release-prep -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/johnhuang316/code-index-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-prep .github/skills/release-prep && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-prep" agent skill from https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prep into .github/skills/release-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-prep", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add johnhuang316/code-index-mcp --skill release-prep -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install johnhuang316/code-index-mcp release-prep --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johnhuang316/code-index-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-prep .opencode/skills/release-prep && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-prep" agent skill from https://github.com/johnhuang316/code-index-mcp/tree/master/.agents/skills/release-prep into .opencode/skills/release-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-prep", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-prep- GitHub stars
- 1k
- Token cost
- ~680 tokens
- SKILL.md length
- 331 words
- Files
- 3 (incl. scripts, references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.
- Works in 9 steps: From the repository root, run → Review changes since the latest v* tag… → After confirmation, run the full test… → …
- Code-index-mcp implementation is complete and a version bump
- SKILL.md covers Overview, When to Use, Required Gates and Workflow, plus 2 more sections
- Runs Python scripts from its folder; calls uv
What it does
Release Prep is an agent skill from johnhuang316/code-index-mcp. Use when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/release_checklist.md` and `scripts/run_release_checks.py`).
It sits in Development, covering Changelog and release notes and MCP servers. It works with GitHub and Model Context Protocol. The repository describes itself as: A Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup. The licence is MIT.
When your agent uses it
- Code-index-mcp implementation is complete and a version bump
- Package publication
- GitHub release is being prepared
Example prompts
- “/release-prep”
Requirements
- Python 3
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- From the repository root, run
- Review changes since the latest v* tag and recommend
- After confirmation, run the full test suite using the checklist command.
- Update all four release artifacts
- Review a release-only diff and rerun the preflight checks.
- Commit with chore(release): vX.Y.Z.
- Draft user-facing release notes and obtain confirmation.
- Only when authorized, create the annotated tag, push the branch and tag, and
- Verify the remote tag, release, and related CI or publication jobs.
What it can do on your machine
Read from SKILL.md and the folder at commit d395cbf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Prep loads about 680 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 331 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from johnhuang316/code-index-mcp at commit d395cbf, republished under its MIT licence (© johnhuang316). 331 words, ~680 tokens.
Download SKILL.mdSave it as
.claude/skills/release-prep/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- release-prep
- description
- Use when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.
Release Prep
Overview
Prepare code-index-mcp releases from a verified commit with an explicit version and release target. The reference checklist owns exact commands; this file owns the decision points and safety gates.
When to Use
- Implementation is complete and ready for a versioned release.
- The user requests a semver recommendation, version bump, release notes, tag, or GitHub release.
- A release candidate needs a final repository and test check.
Do not use during ordinary implementation or when the user has excluded release work.
Required Gates
- Stop on a dirty working tree or an unintended branch.
- Confirm the target version and release branch with the user before editing.
- Confirm release notes before creating a tag or GitHub release.
- Treat pushes, tags, package publication, and GitHub releases as separate external actions requiring user authorization.
Workflow
- From the repository root, run
uv run python .agents/skills/release-prep/scripts/run_release_checks.py; resolve every failed precondition. - Review changes since the latest
v*tag and recommend:patch: bug fixes or user-visible corrections without new surface areaminor: backward-compatible features or capability expansionsmajor: breaking API/behavior changes or migration-required releases
- After confirmation, run the full test suite using the checklist command.
- Update all four release artifacts:
pyproject.toml,src/code_index_mcp/__init__.py,.well-known/mcp.llmfeed.json, anduv.lock. Regenerateuv.lock; never hand-edit it. - Review a release-only diff and rerun the preflight checks.
- Commit with
chore(release): vX.Y.Z. - Draft user-facing release notes and obtain confirmation.
- Only when authorized, create the annotated tag, push the branch and tag, and create the GitHub release.
- Verify the remote tag, release, and related CI or publication jobs.
Resources
| Resource | Use |
|---|---|
scripts/run_release_checks.py | Check repository state, latest tag, and version files; invoke it with the command above. |
references/release_checklist.md | Follow the exact commands and file checklist, resolving paths relative to this skill directory. |
Common Mistakes
- Choosing a version from commit count instead of user-visible compatibility.
- Updating only three of the four release artifacts.
- Including unrelated changes in the release commit.
- Treating a local tag as proof that the release was published.
© johnhuang316, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts, references) in .agents/skills/release-prep of johnhuang316/code-index-mcp.
- SKILL.md
- references/release_checklist.md
- scripts/run_release_checks.py
Open the folder on GitHubat commit d395cbf
Compare with similar skills
Release Prep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Prep this skilljohnhuang316/code-index-mcp | 1k | — | ~680 | Automated safety check: Pass | MIT | |
| Suede Launch PackagingJasonColapietro/suede-creator-skills | 127 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Project Releaseswimmwatch/cloakbrowser-mcp | 161 | — | ~1.9k | Automated safety check: Pass | MIT | |
| ReleasePrefectHQ/fastmcp | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Library Documentation Seekerwithkynam/vibecode-pro-max-kit | 1.1k | 2 repos | ~1k | Automated safety check: Notes | MIT | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
Library Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
Git Release
wesammustafa/opencode-primer
Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable gh release create command.
More from johnhuang316/code-index-mcp
Verify Multilang Support
johnhuang316/code-index-mcp
A skill your agent uses when validating code-index-mcp language strategies, tree-sitter symbol extraction, calledby or import baselines, or sample projects under test/sample-projects after parser…
Related
Works with
Categories
Questions about Release Prep
What does Release Prep do?
A skill your agent uses when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared. Release Prep is an agent skill from johnhuang316/code-index-mcp. Use when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.
When should I use Release Prep?
Release Prep fits situations like: code-index-mcp implementation is complete and a version bump; package publication; GitHub release is being prepared.
How do I install Release Prep in Claude Code?
Run `npx skills add johnhuang316/code-index-mcp --skill release-prep -a claude-code`. Or copy the skill folder (.agents/skills/release-prep in johnhuang316/code-index-mcp) into .claude/skills/release-prep in your project. Claude Code loads it when a task matches its description.
How do I install Release Prep in Codex?
Run `npx skills add johnhuang316/code-index-mcp --skill release-prep -a codex`. Or copy the skill folder (.agents/skills/release-prep in johnhuang316/code-index-mcp) into .agents/skills/release-prep in your project. Codex loads it when a task matches its description.
Can I use Release Prep in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add johnhuang316/code-index-mcp --skill release-prep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-prep, .gemini/skills/release-prep, .github/skills/release-prep and .opencode/skills/release-prep in your project.
What does Release Prep need to run?
Going by SKILL.md and its folder, Release Prep needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Release Prep access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Prep safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Release Prep use?
Release Prep is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Prep use?
About 680 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 461 tokens, read only when the agent opens those files.
What are the alternatives to Release Prep?
Skills that share tags, products or a category with Release Prep: Suede Launch Packaging (JasonColapietro/suede-creator-skills, 127 stars), Project Release (swimmwatch/cloakbrowser-mcp, 161 stars), Release (PrefectHQ/fastmcp, 28k stars) and Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Prep?
johnhuang316 (a GitHub user) maintains it in johnhuang316/code-index-mcp, which has 1,001 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 27, 2026.
Source: johnhuang316/code-index-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.