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 BUZZARDGTA in BUZZARDGTA/Session-Sniffer

Prepare and commit a Session Sniffer release by updating the version in pyproject.toml with the current UTC build timestamp, incrementing the RC or final version as requested, synchronizing uv.lock…

GPL-3.0Auto-check passed

Install Release

skills CLI
$ npx skills add BUZZARDGTA/Session-Sniffer --skill release -a claude-code

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

GitHub CLI
$ gh skill install BUZZARDGTA/Session-Sniffer 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/BUZZARDGTA/Session-Sniffer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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
104
Token cost
~1.3k tokens
SKILL.md length
626 words
Files
3 (incl. scripts)
Skills in repo
3
Repo updated
First seen
Licence
GPL-3.0

At a glance

Prepare and commit a Session Sniffer release by updating the version in pyproject.toml with the current UTC build timestamp, incrementing the RC or final version as requested, synchronizing uv.lock…

  • Works in 12 steps: Inspect the Git working tree before… → Do not modify or discard unrelated user… → Read the current version from… → …
  • SKILL.md covers Release Procedure, Version Format, Unpublished / Untagged Releases and RC Releases, plus 4 more sections
  • Runs Python scripts from its folder; calls uv and git

What it does

Release is an agent skill from BUZZARDGTA/Session-Sniffer. Prepare and commit a Session Sniffer release by updating the version in pyproject.toml with the current UTC build timestamp, incrementing the RC or final version as requested, synchronizing uv.lock via uv lock, validating the change, and creating the release commit.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/__init__.py` and `scripts/update_version.py`).

It works with GitHub. The repository describes itself as: A packet sniffer (also known as an IP sniffer/puller) specifically designed for Peer-To-Peer (P2P) video games on PC and consoles (PlayStation and Xbox). The licence is GPL-3.0.

Example prompts

  • “/release”

Requirements

  • Python 3

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the Git working tree before making changes.
  2. Do not modify or discard unrelated user changes.
  3. Read the current version from pyproject.toml.
  4. Check whether the current version has already been published/tagged on GitHub (git ls-remote --tags origin or local tags matching the…
  5. Generate the current UTC timestamp in the format
  6. Update the version in pyproject.toml
  7. Synchronize uv.lock immediately
  8. Review the resulting diff (both pyproject.toml and uv.lock should reflect the new version).
  9. Run the relevant project validation before committing.
  10. Verify CRLF (\r\n) line endings on all modified files, especially uv.lock and pyproject.toml.
  11. Show the user
  12. Create exactly one version-bump commit containing both pyproject.toml and uv.lock using

What it can do on your machine

Read from SKILL.md and the folder at commit 980ccb5. 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 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • uv
    • git

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

  • Network

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

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

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 BUZZARDGTA/Session-Sniffer at commit 980ccb5, republished under its GPL-3.0 licence (© BUZZARDGTA). 626 words, ~1,251 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
release
description
Prepare and commit a Session Sniffer release by updating the version in pyproject.toml with the current UTC build timestamp, incrementing the RC or final version as requested, synchronizing uv.lock via uv lock, validating the change, and creating the release commit.

Session Sniffer Release

Use this skill when the user wants to prepare and commit a new Session Sniffer release or release candidate.

Release Procedure

  1. Inspect the Git working tree before making changes.
  2. Do not modify or discard unrelated user changes.
  3. Read the current version from pyproject.toml.
  4. Check whether the current version has already been published/tagged on GitHub (git ls-remote --tags origin or local tags matching the version prefix):
    • If NOT tagged/published on GitHub: do NOT increment the RC or version number; only update the build timestamp.
    • If ALREADY tagged/published on GitHub: ask the user whether this is a new release candidate (RC) or a final release.
  5. Generate the current UTC timestamp in the format:
    • build timestamp: YYYYMMDD.HHMM
    • full UTC timestamp: YYYY-MM-DDTHH:MM:SSZ
  6. Update the version in pyproject.toml:
    • If unpublished: preserve the existing version prefix (e.g. v1.5.0rc.69) and update only the build timestamp.
    • For a new RC: increment the existing rc.N number by one, preserving X.Y.Z.
    • For a final release: remove the rc.N suffix, preserving X.Y.Z.
    • Always append the new UTC build timestamp: +YYYYMMDD.HHMM
  7. Synchronize uv.lock immediately:
    • Run uv lock to rebuild/update the session-sniffer version in uv.lock.
    • Enforce CRLF (\r\n) line endings on uv.lock (since uv outputs LF line endings by default).
    • Run uv lock --check to verify the lockfile is completely synchronized.
  8. Review the resulting diff (both pyproject.toml and uv.lock should reflect the new version).
  9. Run the relevant project validation before committing.
  10. Verify CRLF (\r\n) line endings on all modified files, especially uv.lock and pyproject.toml.
  11. Show the user:
    • previous version,
    • new version,
    • changed files (pyproject.toml, uv.lock),
    • validation performed.
  12. Create exactly one version-bump commit containing both pyproject.toml and uv.lock using:

build: bump version to <new-version>

  1. Ensure the version-bump commit is pushed before creating any GitHub tag or release. The release tag MUST match version in pyproject.toml exactly.
  2. Do not amend, reset, rebase, force-push, or otherwise rewrite Git history.

Version Format

The expected version format is:

vMAJOR.MINOR.PATCH+YYYYMMDD.HHMM

or for release candidates:

vMAJOR.MINOR.PATCHrc.N+YYYYMMDD.HHMM

Examples:

v1.5.0rc.45+20260909.2017

v1.5.0+20260909.2017

Unpublished / Untagged Releases

If the current version in pyproject.toml has not been published or tagged on GitHub (e.g. no remote tag exists matching the current version prefix, such as v1.5.0rc.69):

  • Do NOT increment the version number or rc.N number.
  • Retain the exact existing version prefix.
  • Only update the UTC build timestamp (+YYYYMMDD.HHMM).

For example, if the current version is:

v1.5.0rc.69+20260929.0504

and rc.69 was never tagged or published on GitHub, the next build timestamp update becomes:

v1.5.0rc.69+<current UTC timestamp>

Show full SKILL.md (212 more words)Show less

RC Releases

If the current version is:

v1.5.0rc.44+20260908.1641

the next RC must become:

v1.5.0rc.45+<current UTC timestamp>

Do not reuse the previous timestamp.

Final Releases

If the current version is:

v1.5.0rc.45+20260909.2017

a final release of version 1.5.0 becomes:

v1.5.0+<current UTC timestamp>

Do not retain the rc.N suffix.

If the user intends a different X.Y.Z final version, confirm that version before changing the file.

Commit

The commit subject must be:

build: bump version to <new-version>

For example:

build: bump version to v1.5.0rc.45+20260909.2017

The version-bump commit should contain only the intended release-version changes in pyproject.toml and uv.lock. Never commit a release version bump without its synchronized uv.lock.

Do not create a commit if validation fails.

Validation

Use the project's existing validation configuration in pyproject.toml.

For a version-only change, use the smallest relevant validation available:

  • Run uv lock --check to ensure uv.lock is strictly up to date.
  • Verify CRLF (\r\n) line endings on both pyproject.toml and uv.lock.

If dependencies, resources, packaging configuration, or other release-sensitive files are also changed, broaden validation appropriately.

Never claim validation was performed unless it was actually performed.

Important

The version timestamp represents the current UTC time.

Do not use local time.

Do not manually invent or reuse a timestamp.

Do not silently change unrelated files.

Do not automatically push the commit.

© BUZZARDGTA, GPL-3.0. 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) in .agents/skills/release of BUZZARDGTA/Session-Sniffer.

  • SKILL.md
  • scripts/__init__.py
  • scripts/update_version.py

Open the folder on GitHubat commit 980ccb5

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 skillBUZZARDGTA/Session-Sniffer104—~1.3kAutomated safety check: PassGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.8k tokensUpdated today
    Research & ScienceAuto-check: notes

More from BUZZARDGTA/Session-Sniffer

  • Fix

    BUZZARDGTA/Session-Sniffer

    Diagnose and fix Session Sniffer bugs, errors, tracebacks, logs, lint failures, static-analysis findings, test failures, and IDE-reported problems.

    104 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Commit

    BUZZARDGTA/Session-Sniffer

    Organize and commit current Git changes by committing a requested feature alone or splitting all unrelated changes into separate logical commits.

    104 GitHub stars~834 tokensUpdated today
    Auto-check passed

Works with

Questions about Release

What does Release do?

Prepare and commit a Session Sniffer release by updating the version in pyproject.toml with the current UTC build timestamp, incrementing the RC or final version as requested, synchronizing uv.lock…. Release is an agent skill from BUZZARDGTA/Session-Sniffer.lock via uv lock, validating the change, and creating the release commit.

How do I install Release in Claude Code?

Run `npx skills add BUZZARDGTA/Session-Sniffer --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in BUZZARDGTA/Session-Sniffer) 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 BUZZARDGTA/Session-Sniffer --skill release -a codex`. Or copy the skill folder (.agents/skills/release in BUZZARDGTA/Session-Sniffer) 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 BUZZARDGTA/Session-Sniffer --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 Python for the scripts in its folder and the command-line tools its instructions call (uv and git). Our summary lists: Python 3.

Does Release access the network?

SKILL.md contains no URLs. Its commands use uv and git, 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Release use?

Release is published under the GPL-3.0 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.3k tokens (SKILL.md is roughly 5k 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: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

BUZZARDGTA (a GitHub user) maintains it in BUZZARDGTA/Session-Sniffer, which has 104 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

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