Agent skill

Commit

by TypedDevs in TypedDevs/bashunit

Stage and commit changes using conventional commits format. An agent skill from TypedDevs/bashunit.

MITAuto-check: notesDevelopment

Install Commit

skills CLI
$ npx skills add TypedDevs/bashunit --skill commit -a claude-code

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

GitHub CLI
$ gh skill install TypedDevs/bashunit 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/TypedDevs/bashunit.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
434
Token cost
~781 tokens
SKILL.md length
332 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Stage and commit changes using conventional commits format. An agent skill from TypedDevs/bashunit.

  • Works in 7 steps: Review the state above — understand what… → Stage files — add only the relevant… → Determine the commit type from the… → …
  • Tasks that involve Commit messages
  • SKILL.md covers Current State, Arguments, Instructions and Examples, plus 1 more section
  • Calls git

What it does

Commit is an agent skill from TypedDevs/bashunit. Stage and commit changes using conventional commits format

Its SKILL.md is about 780 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 Bash and Git. The repository describes itself as: A simple yet powerfull testing library for bash scripts. The licence is MIT.

When your agent uses it

  • Tasks that involve Commit messages

Example prompts

  • “/commit”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob

Workflow steps

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

  1. Review the state above — understand what changed and why.
  2. Stage files — add only the relevant changed files by name. Never use git add -A or git add .. Never stage files that contain secrets…
  3. Determine the commit type from the nature of the changes
  4. Determine the scope from the area of the codebase affected
  5. Write the commit message
  6. Create the commit
  7. Verify the commit was created

What it can do on your machine

Read from SKILL.md and the folder at commit 8f297fb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Glob

    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 781 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 332 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
~781

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

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:30
    Never stage files that contain secrets (`.env`, credentials, etc.).
  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Glob

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 TypedDevs/bashunit at commit 8f297fb, republished under its MIT licence (© TypedDevs). 332 words, ~781 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Stage and commit changes using conventional commits format
allowed-tools
Bash, Read, Grep, Glob
user-invocable
true
argument-hint
[message hint]
disable-model-invocation
true

Commit with Conventional Commits

Stage and commit current changes using the conventional commits format.

IMPORTANT: This skill MUST be used for ALL commits — even when the user says "commit" without /commit. Never commit without following these steps.

Current State

  • Branch: !git branch --show-current
  • Status: !git status --short
  • Staged diff: !git diff --cached --stat 2>/dev/null
  • Unstaged diff: !git diff --stat 2>/dev/null
  • Recent commits: !git log --oneline -5 2>/dev/null

Arguments

  • $ARGUMENTS - Optional hint for the commit message (e.g., fix the snapshot comparison)

Instructions

  1. Review the state above — understand what changed and why.

  2. Stage files — add only the relevant changed files by name. Never use git add -A or git add .. Never stage files that contain secrets (.env, credentials, etc.).

  3. Determine the commit type from the nature of the changes:

    • feat — new feature or capability
    • fix — bug fix
    • docs — documentation only
    • style — formatting, whitespace (no logic change)
    • refactor — code restructuring (no behavior change)
    • test — adding or updating tests
    • chore — maintenance, tooling, config
    • perf — performance improvement
  4. Determine the scope from the area of the codebase affected:

    • assert — assertions (src/assert*.sh)
    • runner — test runner
    • cli — CLI entry point, flags, options
    • doubles — mocks, spies
    • docs — documentation site
    • ci — CI/CD, GitHub Actions
    • Use the most specific scope that fits. Omit if changes span many areas.
  5. Write the commit message:

    • Format: <type>(<scope>): <description>
    • Description: imperative mood, lowercase, no period, under 70 chars
    • Focus on why, not what
    • Add a body (separated by blank line) only if the why isn't obvious from the description
    • Never mention AI, Claude, or automation in the message
  6. Create the commit:

    bash
    git commit -m "$(cat <<'EOF'
    <type>(<scope>): <description>
    
    <optional body>
    EOF
    )"
  7. Verify the commit was created:

    bash
    git log --oneline -1

Examples

feat(assert): add assert_json_contains function
fix(runner): resolve parallel execution race condition
test(doubles): add spy verification edge cases
refactor(cli): extract option parsing into helper
docs: update installation instructions
chore(ci): upgrade shellcheck to v0.10
perf(runner): reduce subshell usage in test discovery

Rules

  • One logical change per commit — don't mix unrelated changes
  • Never use --no-verify — if hooks fail, fix the issue
  • Never amend unless the user explicitly asks
  • Always create a NEW commit — even after a hook failure
  • Author: use the git config identity (never commit as sandbox/default user)

© TypedDevs, 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 .claude/skills/commit of TypedDevs/bashunit.

Open the folder on GitHubat commit 8f297fb

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 skillTypedDevs/bashunit434—~781Automated safety check: NotesMIT
Commitalex35mil/dotfiles301—~438Automated safety check: WarnNone
Commitmeain/dotfiles285—~723Automated 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

Similar skills

  • Commit

    alex35mil/dotfiles

    Creates a git commit for the current repository using this repo's commit style.

    301 GitHub stars~438 tokensUpdated 1 mo ago
    DevelopmentAuto-check: warnings
  • Commit

    meain/dotfiles

    Create git commits for dotfiles changes, grouping by component with conventional prefix style

    285 GitHub stars~723 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • 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
  • 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

More from TypedDevs/bashunit

All 11 skills in this repo
  • Gh Issues

    TypedDevs/bashunit

    Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

    434 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check: notes
  • Gh Issue

    TypedDevs/bashunit

    Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

    434 GitHub stars~721 tokensUpdated today
    Auto-check: notes
  • PR

    TypedDevs/bashunit

    Push branch and create a GitHub PR with concise, issue-linked description

    434 GitHub stars~1k tokensUpdated today
    Auto-check: notes
  • Pre Release

    TypedDevs/bashunit

    Run comprehensive pre-release validation checklist. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~488 tokensUpdated today
    Auto-check: notes
  • Release

    TypedDevs/bashunit

    Run pre-release validation and execute the release process. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~618 tokensUpdated today
    Auto-check: notes
  • Check Coverage

    TypedDevs/bashunit

    Analyze test coverage and identify untested code paths. An agent skill from TypedDevs/bashunit.

    434 GitHub starsUsed in 1 repo~326 tokens
    Auto-check: notes

Works with

Categories

Questions about Commit

What does Commit do?

Stage and commit changes using conventional commits format. An agent skill from TypedDevs/bashunit. Commit is an agent skill from TypedDevs/bashunit.

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 TypedDevs/bashunit --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in TypedDevs/bashunit) 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 TypedDevs/bashunit --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in TypedDevs/bashunit) 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 TypedDevs/bashunit --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). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob.

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 notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. 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 781 tokens (SKILL.md is roughly 3.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?

Skills that share tags, products or a category with Commit: Commit (alex35mil/dotfiles, 301 stars), Commit (meain/dotfiles, 285 stars), React Router Release Notes Prep (remix-run/react-router, 57k stars) and ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

TypedDevs (a GitHub organization) maintains it in TypedDevs/bashunit, which has 434 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

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