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 Changes

by debuglebowski in debuglebowski/slayzone

Commit the changes that has been worked on in this session. An agent skill from debuglebowski/slayzone.

GPL-3.0Auto-check passedDevelopment

Install Commit Changes

skills CLI
$ npx skills add debuglebowski/slayzone --skill commit-changes -a claude-code

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

GitHub CLI
$ gh skill install debuglebowski/slayzone commit-changes --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/debuglebowski/slayzone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-changes .claude/skills/commit-changes && 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-changes
GitHub stars
191
Token cost
~531 tokens
SKILL.md length
300 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
GPL-3.0

At a glance

Commit the changes that has been worked on in this session. An agent skill from debuglebowski/slayzone.

  • Tasks that involve Commit messages
  • SKILL.md covers Workflow and Safety rules
  • Calls git

What it does

Commit Changes is an agent skill from debuglebowski/slayzone. Commit the changes that has been worked on in this session

Its SKILL.md is about 530 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 licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Commit messages

Example prompts

  • “/commit-changes”

What it can do on your machine

Read from SKILL.md and the folder at commit e912716. 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 Changes loads about 531 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 300 words of instructions outside code blocks.

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

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 debuglebowski/slayzone at commit e912716, republished under its GPL-3.0 licence (© debuglebowski). 300 words, ~531 tokens.

Download SKILL.mdSave it as .claude/skills/commit-changes/SKILL.md (or your agent's skills folder).
name
commit-changes
description
Commit the changes that has been worked on in this session
trigger
auto

Prepare a git commit for the current task. User context: $ARGUMENTS

Workflow

  1. Inspect repository state.
  • Run git status --short.
  • Run git diff --name-only and git diff --cached --name-only.
  1. Build a candidate set from current-task work only.
  • Include files and hunks created or edited for the current request.
  • Exclude pre-existing, unrelated, or user-authored edits that were not part of this task.
  • If confidence is not high for any file or hunk, mark it as uncertain.
  1. Resolve uncertainty before staging.
  • If any file or hunk is uncertain, stop and ask the user exactly what to include.
  • Ask with explicit paths/hunks so the user can approve or exclude each uncertain change.
  • Do not commit until all uncertain items are resolved.
  1. Stage explicit paths/hunks only.
  • Use git add <file1> <file2> ....
  • Use git add -p <file> when only part of a file belongs in this commit.
  • Do not use git add . or git add -A unless the user explicitly asks to commit everything.
  1. Validate staged content.
  • Run git diff --cached.
  • Confirm staged hunks are only the current-task edits and do not include accidental or unrelated changes.
  1. Write a Conventional Commit message.
  • Use one type: feat, fix, chore, refactor, docs, test.
  • Optional scope format: type(scope): summary.
  • Keep the subject concise and imperative.
  1. Commit non-interactively.
  • Run git commit -m "<message>".
  • Do not use interactive commit flows.
  • Do not amend existing commits unless the user explicitly asks.
  1. Report completion.
  • Provide commit hash, commit subject, and file list.
  • Also report remaining modified or untracked files.

Safety rules

  • Never revert user changes unless explicitly instructed.
  • Never run destructive commands (git reset --hard, force checkout) unless explicitly instructed.
  • Never include a change with unclear ownership; ask the user first.
  • Prefer one focused commit per user request unless asked to split into multiple commits.

© debuglebowski, 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-changes of debuglebowski/slayzone.

Open the folder on GitHubat commit e912716

Compare with similar skills

Commit Changes 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 Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Changes this skilldebuglebowski/slayzone191—~531Automated 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 today
    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 today
    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 today
    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 today
    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 debuglebowski/slayzone

All 16 skills in this repo

  • Comparison Page

    debuglebowski/slayzone

    Create or update objective website comparison pages and head-to-head pages from the comparison canon.

    191 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Slay Artifacts

    debuglebowski/slayzone

    Manage task artifacts (files, folders) via the slay CLI. An agent skill from debuglebowski/slayzone.

    191 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Slay Automations

    debuglebowski/slayzone

    Create and manage automations via the slay CLI. An agent skill from debuglebowski/slayzone.

    191 GitHub stars~627 tokensUpdated 1 mo ago
    Auto-check passed

  • Slay Orchestrate

    debuglebowski/slayzone

    Supervise a set of slay tasks through planning, execution, and verification

    191 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Slay Context

    debuglebowski/slayzone

    Ensure root instruction files include SlayZone environment context

    191 GitHub stars~448 tokensUpdated 1 mo ago
    Auto-check passed

  • Slay Pty

    debuglebowski/slayzone

    Interact with PTY terminal sessions via the slay CLI. An agent skill from debuglebowski/slayzone.

    191 GitHub stars~916 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Commit Changes

What does Commit Changes do?

Commit the changes that has been worked on in this session. An agent skill from debuglebowski/slayzone. Commit Changes is an agent skill from debuglebowski/slayzone.

When should I use Commit Changes?

Commit Changes fits situations like: tasks that involve Commit messages.

How do I install Commit Changes in Claude Code?

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

How do I install Commit Changes in Codex?

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

Can I use Commit Changes 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 debuglebowski/slayzone --skill commit-changes -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-changes, .gemini/skills/commit-changes, .github/skills/commit-changes and .opencode/skills/commit-changes in your project.

What does Commit Changes need to run?

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

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

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

About 531 tokens (SKILL.md is roughly 2.1k 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 Changes?

Skills that share tags, products or a category with Commit Changes: 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 Changes?

debuglebowski (a GitHub user) maintains it in debuglebowski/slayzone, which has 191 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 3, 2026.

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