New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release

by xin2017338 in xin2017338/lynx-proxy

Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add xin2017338/lynx-proxy --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install xin2017338/lynx-proxy release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/xin2017338/lynx-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release
GitHub stars
502
Token cost
~1.1k tokens
SKILL.md length
357 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.

  • Works in 9 steps: Determine Version → Run Tests & Lint → Update CHANGELOG → …
  • : user says publish
  • SKILL.md covers When to Use, Prerequisites, Release Procedure and Important Notes, plus 1 more section
  • Calls git, cargo and npm

What it does

Release is an agent skill from xin2017338/lynx-proxy. Publish a new release version of Lynx Proxy. Use when: user says "publish", "release", "发版", "发布版本", "打 tag", "bump version". Steps: version bump → test & lint → changelog → UI build → schema export → commit → tag → push → trigger CI.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Linting and formatting. It works with Rust and Git. The repository describes itself as: Lynx Proxy is a high-performance and flexible proxy tool developed in Rust. The licence is MIT.

When your agent uses it

  • : user says publish
  • Tasks that involve Changelog and release notes
  • Tasks that involve Linting and formatting

Example prompts

  • “publish”
  • “release”
  • “bump version”
  • “/release”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Determine Version
  2. Run Tests & Lint
  3. Update CHANGELOG
  4. Bump Version (Root Cargo.toml)
  5. Build UI Assets
  6. Export Rules Schema
  7. Commit & Tag
  8. Push to GitHub
  9. (Optional) Quick Release with cargo-release

What it can do on your machine

Read from SKILL.md and the folder at commit 96b6d7a. 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

    Shell commands in SKILL.md call:

    • git
    • cargo
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, 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 loads about 1.1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 357 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from xin2017338/lynx-proxy at commit 96b6d7a, republished under its MIT licence (© xin2017338). 357 words, ~1,100 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Publish a new release version of Lynx Proxy. Use when: user says "publish", "release", "发版", "发布版本", "打 tag", "bump version". Steps: version bump → test & lint → changelog → UI build → schema export → commit → tag → push → trigger CI.
argument-hint
version type: patch | minor | major (default: patch)

Lynx Proxy Release Process

When to Use

  • User asks to publish a new version / 发布版本
  • User asks to bump version / 升级版本
  • User asks to trigger CI build / 触发流水线构建
  • User asks to create a release / 创建 Release

Prerequisites

  • Working directory: /Users/wx/codes/lynx-proxy
  • Rust toolchain: stable (rustfmt + clippy)
  • Installed tools: cargo-release, git-cliff, task
  • UI dependencies: npm ci in ui/
  • Git: clean working tree (no uncommitted changes)
  • All tests pass and linter is clean (see step 2)

Release Procedure

1. Determine Version

Check current version from Cargo.toml:

workspace.package.version

Determine the new version based on changes:

  • patch (0.8.4 → 0.8.5): Bug fixes only
  • minor (0.8.4 → 0.9.0): New features, backward compatible
  • major (0.8.4 → 1.0.0): Breaking changes
2. Run Tests & Lint

⚠️ Never release without passing tests!

bash
# Run all workspace tests
cargo test --workspace

# Run clippy linter (deny warnings)
cargo clippy --all-targets --all-features -- -D warnings

# Check formatting
cargo fmt --all -- --check

Or use the Taskfile:

bash
task lint
task test
3. Update CHANGELOG

Update CHANGELOG.md:

  • Add a new section ## [<version>] - <YYYY-MM-DD>
  • Group changes under conventional commit categories:
    • ### 🚀 Features
    • ### 🐛 Bug Fixes
    • ### ♻️ Refactor
    • ### 📚 Documentation
    • ### 🧪 Testing
    • ### ⚙️ Miscellaneous Tasks
  • Use format: - *(<scope>)* <description>

Alternatively, generate from git history:

bash
git-cliff --unreleased --tag v<version> --prepend CHANGELOG.md
4. Bump Version (Root Cargo.toml)

Update the version field in Cargo.toml under [workspace.package]:

version = "<new_version>"

⚠️ All sub-crates use version.workspace = true, so only the root Cargo.toml needs updating.

5. Build UI Assets
bash
cd /Users/wx/codes/lynx-proxy && task build-ui

This generates the Vue.js frontend into crates/lynx-cli/assets/.

6. Export Rules Schema
bash
cargo run -q -p lynx-cli -- rules schema export --out schemas/rules-export.schema.json
7. Commit & Tag
bash
git add -A
git commit -m "chore(release): v<version>"
git tag v<version>
Show full SKILL.md (159 more words)Show less
8. Push to GitHub
bash
git push origin main
git push origin v<version>

This triggers the Release GitHub Actions workflow (.github/workflows/release.yml), which:

  1. Builds the UI assets
  2. Runs cargo-dist to build binaries for:
    • aarch64-apple-darwin (macOS ARM)
    • x86_64-unknown-linux-gnu (Linux x86_64)
    • x86_64-pc-windows-msvc (Windows x86_64)
  3. Creates a GitHub Release with artifacts and installer scripts
9. (Optional) Quick Release with cargo-release

For a fully automated flow:

bash
# Patch release
cargo release patch --execute

# Minor release
cargo release minor --execute

# Major release  
cargo release major --execute

This uses the config in release.toml:

  • Pre-release hook: task build-ui
  • Pre-tag hook: exports rules schema
  • No crates.io publish (publish = false)
  • Auto-push to git

Important Notes

  • Tests are mandatory: The Taskfile release tasks (release-patch, release-minor, release-alpha) all declare test as a dependency — they will refuse to run if tests fail.
  • No crates.io publish: release.toml sets publish = false. GitHub Actions handles binary distribution.
  • Tag format: v<semver> (e.g., v0.8.4), triggers .github/workflows/release.yml.
  • Changelog convention: Keep CHANGELOG.md with ## [<version>] - <YYYY-MM-DD> headers.
  • Commit convention: Use conventional commits (feat:, fix:, chore:, etc.) for changelog generation.
  • After release: Verify the GitHub Actions workflow at https://github.com/xin2017338/lynx-proxy/actions.

Rollback

If something goes wrong after pushing:

bash
# Delete remote tag
git push --delete origin v<version>

# Delete local tag
git tag -d v<version>

# Revert commit
git revert HEAD
git push origin main

© xin2017338, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/release of xin2017338/lynx-proxy.

Open the folder on GitHubat commit 96b6d7a

Compare with similar skills

Release 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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillxin2017338/lynx-proxy502—~1.1kAutomated safety check: PassMIT
Release Procedurexberg-io/alef100—~3kAutomated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9k—~6.9kAutomated safety check: PassCustom licence
PR Pushicebear0828/codex-proxy1.8k—~2.2kAutomated safety check: NotesCustom licence
PR Pushicebear0828/codex-proxy1.8k—~2.3kAutomated safety check: NotesCustom licence
Prepare Releasefrozenlib/parse-display193—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Release Procedure

    xberg-io/alef

    Cut, tag, and publish an alef release end-to-end. An agent skill from xberg-io/alef.

    100 GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check: notes

  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check: notes

  • Prepare Release

    frozenlib/parse-display

    Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available.

    193 GitHub stars~1.3k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Leanspec Development

    codervisor/leanspec

    Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec.

    296 GitHub stars~2.5k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

Works with

Categories

Questions about Release

What does Release do?

Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy. Release is an agent skill from xin2017338/lynx-proxy. Publish a new release version of Lynx Proxy.

When should I use Release?

Release fits situations like: : user says publish; tasks that involve Changelog and release notes; tasks that involve Linting and formatting.

How do I install Release in Claude Code?

Run `npx skills add xin2017338/lynx-proxy --skill release -a claude-code`. Or copy the skill folder (.github/skills/release in xin2017338/lynx-proxy) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add xin2017338/lynx-proxy --skill release -a codex`. Or copy the skill folder (.github/skills/release in xin2017338/lynx-proxy) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Release 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 xin2017338/lynx-proxy --skill release -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, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, cargo and npm).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release 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. Review the folder before installing.

What licence does Release use?

Release 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 use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release?

Skills that share tags, products or a category with Release: Release Procedure (xberg-io/alef, 100 stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars), PR Push (icebear0828/codex-proxy, 1.8k stars) and PR Push (icebear0828/codex-proxy, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

xin2017338 (a GitHub user) maintains it in xin2017338/lynx-proxy, which has 502 GitHub stars. The repository was last updated on September 15, 2026.

Source: xin2017338/lynx-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.