New: 97,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

Commit

by BUZZARDGTA in BUZZARDGTA/Session-Sniffer

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

GPL-3.0Auto-check passedDevelopment

Install Commit

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

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

GitHub CLI
$ gh skill install BUZZARDGTA/Session-Sniffer commit --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/commit .claude/skills/commit && 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
commit
GitHub stars
104
Token cost
~834 tokens
SKILL.md length
459 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
GPL-3.0

At a glance

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

  • Works in 6 steps: Inspect the Git working tree and full… → Identify the files and individual diff… → Do not stage unrelated files or hunks. → …
  • Tasks that involve Commit messages
  • SKILL.md covers Commit Modes, Commit Messages, Safety and Validation, plus 1 more section
  • Calls git

What it does

Commit is an agent skill from BUZZARDGTA/Session-Sniffer. Organize and commit current Git changes by committing a requested feature alone or splitting all unrelated changes into separate logical commits.

Its SKILL.md is about 830 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 Commit messages. It works with Git. 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.

When your agent uses it

  • Tasks that involve Commit messages

Example prompts

  • “/commit”

Workflow steps

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

  1. Inspect the Git working tree and full diff.
  2. Identify the files and individual diff hunks belonging to the requested change.
  3. Do not stage unrelated files or hunks.
  4. If the requested change cannot be separated safely from unrelated changes, explain the overlap and ask how the user wants to proceed.
  5. Propose one commit message describing only that change.
  6. Stage only the intended changes and create exactly one commit.

What it can do on your machine

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

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

  • Network

    No URLs in SKILL.md. Its commands use 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

Commit loads about 834 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 459 words of instructions outside code blocks.

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

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 BUZZARDGTA/Session-Sniffer at commit 00fcd76, republished under its GPL-3.0 licence (© BUZZARDGTA). 459 words, ~834 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Organize and commit current Git changes by committing a requested feature alone or splitting all unrelated changes into separate logical commits.

Session Sniffer Commit

Use this skill when the user wants to commit current Git changes.

Commit Modes

Determine the user's intent from the request.

Specific Change

If the user identifies a feature, fix, refactor, documentation change, or other specific change:

  1. Inspect the Git working tree and full diff.
  2. Identify the files and individual diff hunks belonging to the requested change.
  3. Do not stage unrelated files or hunks.
  4. If the requested change cannot be separated safely from unrelated changes, explain the overlap and ask how the user wants to proceed.
  5. Propose one commit message describing only that change.
  6. Stage only the intended changes and create exactly one commit.
All Changes

If the user asks to commit everything, do not automatically create one large commit.

  1. Inspect the Git working tree and full diff.
  2. Group changes into logical, independently meaningful changes.
  3. Separate unrelated features, fixes, refactors, tests, documentation, configuration, and other changes into different commits where practical.
  4. Use file-level and hunk-level staging when necessary.
  5. Do not force a separation when changes are tightly coupled and belong in the same commit.
  6. Propose one commit message for each logical change.
  7. Show the proposed groups, affected files, and commit messages.
  8. Create the proposed commits in logical order.

Commit Messages

Use concise Conventional Commit-style messages when appropriate:

  • feat: for new functionality
  • fix: for bug fixes
  • refactor: for code restructuring without behavior change
  • perf: for performance improvements
  • test: for test-only changes
  • docs: for documentation
  • build: for build/dependency/package changes
  • chore: for maintenance

Write the message from the actual diff. Do not invent functionality or motivation that is not supported by the changes.

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

Safety

  • Never modify files merely to make commits possible.
  • Never include unrelated user changes.
  • Preserve unstaged and uncommitted changes that are outside the selected commit.
  • Use partial/hunk staging when files contain changes belonging to multiple commits.
  • Inspect the staged diff before every commit.
  • Do not use git add . or equivalent blanket staging when only part of the working tree belongs in a commit.
  • Do not amend existing commits.
  • Do not reset, rebase, force-push, or rewrite existing history.
  • Do not push commits unless the user explicitly asks for a push as a separate action.

Validation

Before committing:

  1. Review the staged diff.
  2. Run the smallest relevant validation available for the selected changes when practical.
  3. Do not claim validation was performed unless it actually ran successfully.
  4. If validation fails, stop before committing and report the failure.

For multiple commits, validate each staged change as appropriate before creating its commit.

Final Report

After committing, report:

  • commit hash
  • commit message
  • files included
  • validation performed
  • any remaining unstaged or uncommitted changes

The goal is to produce clean, focused commits while leaving unrelated work untouched.

© 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

Just SKILL.md in .agents/skills/commit of BUZZARDGTA/Session-Sniffer.

Open the folder on GitHubat commit 00fcd76

Compare with similar skills

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

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillBUZZARDGTA/Session-Sniffer104—~834Automated safety check: PassGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Saleor Commit Workflow

    saleor/saleor

    Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

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 3 days ago
    Auto-check passed

  • Release

    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…

    104 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Organize and commit current Git changes by committing a requested feature alone or splitting all unrelated changes into separate logical commits. Commit is an agent skill from BUZZARDGTA/Session-Sniffer. Organize and commit current Git changes by committing a requested feature alone or splitting all unrelated changes into separate logical commits.

When should I use Commit?

Commit fits situations like: tasks that involve Commit messages.

How do I install Commit in Claude Code?

Run `npx skills add BUZZARDGTA/Session-Sniffer --skill commit -a claude-code`. Or copy the skill folder (.agents/skills/commit in BUZZARDGTA/Session-Sniffer) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add BUZZARDGTA/Session-Sniffer --skill commit -a codex`. Or copy the skill folder (.agents/skills/commit in BUZZARDGTA/Session-Sniffer) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit 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 commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

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

Does Commit access the network?

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

Is Commit 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 Commit use?

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

About 834 tokens (SKILL.md is roughly 3.3k 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 Commit?

Skills that share tags, products or a category with Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

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 4, 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.