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

Commit

by sushaantu in sushaantu/boxento

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

MITAuto-check passedDevelopment

Install Commit

skills CLI
$ npx skills add sushaantu/boxento --skill commit -a claude-code

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

GitHub CLI
$ gh skill install sushaantu/boxento 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/sushaantu/boxento.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/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
154
Used in
2 other repos
Token cost
~473 tokens
SKILL.md length
223 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

  • Works in 12 steps: Read session history to identify scope,… → Inspect the working tree and staged… → Stage intended changes, including new… → …
  • Asked to commit
  • SKILL.md covers Goals, Inputs, Steps and Template
  • Calls git and codex

What it does

Commit is an agent skill from sushaantu/boxento. Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

Its SKILL.md is about 470 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: Open-source customizable start page. The licence is MIT.

When your agent uses it

  • Asked to commit
  • Prepare a commit message
  • Finalize staged work

Example prompts

  • “/commit”

Workflow steps

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

  1. Read session history to identify scope, intent, and rationale.
  2. Inspect the working tree and staged changes.
  3. Stage intended changes, including new files, after confirming scope.
  4. Sanity-check newly added files and flag anything that looks like an artifact, log, or temp file.
  5. If staging is incomplete or includes unrelated files, fix the index or ask for confirmation.
  6. Choose a conventional type and optional scope that match the change.
  7. Write a subject line in imperative mood, 72 characters or fewer, without a trailing period.
  8. Write a body that includes
  9. Append a Co-authored-by trailer for Codex using Codex unless the user explicitly requests a different identity.
  10. Wrap body lines at 72 characters.
  11. Create the commit with git commit -F or equivalent so newlines are literal.
  12. Ensure the message matches the staged changes before committing.

What it can do on your machine

Read from SKILL.md and the folder at commit 3209676. 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
    • codex

    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 473 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 223 words of instructions outside code blocks.

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

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 sushaantu/boxento at commit 3209676, republished under its MIT licence (© sushaantu). 223 words, ~473 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

Commit

Goals

  • Produce a commit that reflects the actual code changes and the session context.
  • Follow common git conventions with a concise subject and wrapped body.
  • Include both summary and rationale in the body.

Inputs

  • Codex session history for intent and rationale.
  • git status, git diff, and git diff --staged for actual changes.
  • Repo-specific commit conventions if documented.

Steps

  1. Read session history to identify scope, intent, and rationale.
  2. Inspect the working tree and staged changes.
  3. Stage intended changes, including new files, after confirming scope.
  4. Sanity-check newly added files and flag anything that looks like an artifact, log, or temp file.
  5. If staging is incomplete or includes unrelated files, fix the index or ask for confirmation.
  6. Choose a conventional type and optional scope that match the change.
  7. Write a subject line in imperative mood, 72 characters or fewer, without a trailing period.
  8. Write a body that includes:
    • Summary of key changes.
    • Rationale and trade-offs.
    • Tests or validation run, or an explicit note if not run.
  9. Append a Co-authored-by trailer for Codex using Codex <codex@openai.com> unless the user explicitly requests a different identity.
  10. Wrap body lines at 72 characters.
  11. Create the commit with git commit -F <file> or equivalent so newlines are literal.
  12. Ensure the message matches the staged changes before committing.

Template

text
<type>(<scope>): <short summary>

Summary:
- <what changed>
- <what changed>

Rationale:
- <why>
- <why>

Tests:
- <command or "not run (reason)">

Co-authored-by: Codex <codex@openai.com>

© sushaantu, 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 .codex/skills/commit of sushaantu/boxento.

Open the folder on GitHubat commit 3209676

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sushaantu/boxento, which our catalogue first saw on October 7, 2026.

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 skillsushaantu/boxento1542 repos~473Automated safety check: PassMIT
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-skills103k2 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 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.

    103k 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 today
    DevelopmentAuto-check passed

More from sushaantu/boxento

  • Land

    sushaantu/boxento

    Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

    154 GitHub starsUsed in 1 repo~524 tokens
    Auto-check passed

  • Push

    sushaantu/boxento

    Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create a pull request.

    154 GitHub stars~613 tokensUpdated today
    Auto-check passed

  • Linear

    sushaantu/boxento

    Use Symphony's lineargraphql client tool for raw Linear GraphQL operations such as comment editing and status updates.

    154 GitHub stars~447 tokensUpdated today
    Auto-check passed

  • Pull

    sushaantu/boxento

    Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch).

    154 GitHub stars~445 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work. Commit is an agent skill from sushaantu/boxento. Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

When should I use Commit?

Commit fits situations like: asked to commit; prepare a commit message; finalize staged work.

How do I install Commit in Claude Code?

Run `npx skills add sushaantu/boxento --skill commit -a claude-code`. Or copy the skill folder (.codex/skills/commit in sushaantu/boxento) 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 sushaantu/boxento --skill commit -a codex`. Or copy the skill folder (.codex/skills/commit in sushaantu/boxento) 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 sushaantu/boxento --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 and codex).

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 MIT 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 473 tokens (SKILL.md is roughly 1.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: 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, 103k 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?

sushaantu (a GitHub user) maintains it in sushaantu/boxento, which has 154 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

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