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

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

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

GitHub CLI
$ gh skill install debuglebowski/slayzone 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/debuglebowski/slayzone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
191
Token cost
~718 tokens
SKILL.md length
412 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.

  • Development work in your project
  • SKILL.md covers Default scope: this session only, Workflow and Safety rules
  • Calls git

What it does

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

Its SKILL.md is about 720 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. It works with Git. The licence is GPL-3.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/commit”

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 loads about 718 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 412 words of instructions outside code blocks.

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

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). 412 words, ~718 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
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

Default scope: this session only

Unless the user says otherwise, commit ONLY the changes made in the current session. Do not include pre-existing modifications, untracked files from earlier work, or edits the user made manually outside this session — even if they are staged or in the working tree.

Override signals (commit broader scope only when user explicitly says): "commit everything", "commit all", "include the other changes", "stage X too", or names specific files outside the session set.

Workflow

  1. Inspect repository state.
  • Run git status --short.
  • Run git diff --name-only and git diff --cached --name-only.
  • Cross-reference against this session's tool-call history (Edit/Write/MultiEdit targets) to identify which files this session actually touched.
  1. Build a candidate set from this session's work only.
  • Include only files and hunks this session created or edited.
  • Exclude pre-existing, unrelated, or user-authored edits that were not part of this session — even if they appear in git status.
  • If confidence is not high for any file or hunk (e.g. session edited part of a file, but other hunks predate session), 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.
Show full SKILL.md (138 more words)Show less
  1. Validate staged content.
  • Run git diff --cached.
  • Confirm staged hunks are only this session's 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 .claude/skills/commit of debuglebowski/slayzone.

Open the folder on GitHubat commit e912716

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 skilldebuglebowski/slayzone191—~718Automated safety check: PassGPL-3.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything85k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    85k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    85k GitHub starsUsed in 1 repo~1.3k tokens
    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

What does Commit do?

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

When should I use Commit?

Commit fits situations like: development work in your project.

How do I install Commit in Claude Code?

Run `npx skills add debuglebowski/slayzone --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in debuglebowski/slayzone) 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 debuglebowski/slayzone --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in debuglebowski/slayzone) 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 debuglebowski/slayzone --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 718 tokens (SKILL.md is roughly 2.9k 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: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

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.