Agent skill

Git Commit

by agulli in agulli/atlas-agents

Create well-structured git commits with conventional commit messages.

MITAuto-check: notesDevelopment

Install Git Commit

skills CLI
$ npx skills add agulli/atlas-agents --skill git-commit -a claude-code

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

GitHub CLI
$ gh skill install agulli/atlas-agents git-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/agulli/atlas-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ch09_agent_skills/skills/git-commit .claude/skills/git-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
git-commit
GitHub stars
578
Token cost
~463 tokens
SKILL.md length
207 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Create well-structured git commits with conventional commit messages.

  • Works in 7 steps: Run git status to see all changed files.… → Run git diff --stat to understand the… → Group related changes. If the diff… → …
  • Asked to commit changes
  • SKILL.md covers Process, Rationalizations and Verification
  • Calls git

What it does

Git Commit is an agent skill from agulli/atlas-agents. Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.

Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires git

It sits in Development, covering Commit messages. It works with Git. The licence is MIT.

When your agent uses it

  • Asked to commit changes
  • Prepare a commit
  • Stage and push code

Example prompts

  • “/git-commit”

Requirements

  • Compatibility (from SKILL.md): Requires git
  • Pre-approved tools (allowed-tools): Bash(git:*)

Workflow steps

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

  1. Run git status to see all changed files. Read the output carefully.
  2. Run git diff --stat to understand the scope of the change.
  3. Group related changes. If the diff contains unrelated changes (e.g., a bug fix AND a new feature), create separate commits. Do not bundle…
  4. Stage files intentionally. Use git add , never git add . unless every changed file belongs in the same logical commit.
  5. Write the commit message using Conventional Commits format
  6. Verify before committing. Run git diff --cached to review exactly what will be committed. Read the staged diff.
  7. Commit. Run git commit -m "..." with the message.

What it can do on your machine

Read from SKILL.md and the folder at commit 2b21998. 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(git:*)

    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.

  • Compatibility

    Requires git

    From compatibility in the SKILL.md frontmatter.

Context cost

Git Commit loads about 463 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 207 words of instructions outside code blocks.

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

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:40
    - [ ] No `.env`, `__pycache__`, or build artifacts were staged

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 agulli/atlas-agents at commit 2b21998, republished under its MIT licence (© agulli). 207 words, ~463 tokens.

Download SKILL.mdSave it as .claude/skills/git-commit/SKILL.md (or your agent's skills folder).
name
git-commit
description
Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.
allowed-tools
Bash(git:*)
compatibility
Requires git
license
MIT

Process

  1. Run git status to see all changed files. Read the output carefully.
  2. Run git diff --stat to understand the scope of the change.
  3. Group related changes. If the diff contains unrelated changes (e.g., a bug fix AND a new feature), create separate commits. Do not bundle unrelated work.
  4. Stage files intentionally. Use git add <specific-files>, never git add . unless every changed file belongs in the same logical commit.
  5. Write the commit message using Conventional Commits format:
    <type>(<scope>): <description>
    
    <body — explain WHY, not WHAT>
    
    <footer — references, breaking changes>
    Types: feat, fix, refactor, docs, test, chore, perf, ci
  6. Verify before committing. Run git diff --cached to review exactly what will be committed. Read the staged diff.
  7. Commit. Run git commit -m "..." with the message.

Rationalizations

ExcuseRebuttal
"I'll just use git add . to save time"Staging everything blindly leads to committing debug files, env vars, and unrelated changes. Stage intentionally.
"The message 'fix stuff' is fine for now"Every commit message is permanent history. Write it properly the first time.
"I'll squash these later"You won't. Write clean commits now.

Verification

  • git diff --cached output was reviewed before committing
  • Commit message follows Conventional Commits format
  • No unrelated changes were bundled into a single commit
  • No .env, __pycache__, or build artifacts were staged

© agulli, 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 ch09_agent_skills/skills/git-commit of agulli/atlas-agents.

Open the folder on GitHubat commit 2b21998

Compare with similar skills

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

Git Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Commit this skillagulli/atlas-agents578—~463Automated safety check: NotesMIT
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
  • 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
  • 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
  • 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 agulli/atlas-agents

All 12 skills in this repo
  • API Design

    agulli/atlas-agents

    Design or review REST and GraphQL API interfaces. An agent skill from agulli/atlas-agents.

    578 GitHub stars~539 tokensUpdated 2 mo ago
    Auto-check passed
  • Data Pipeline

    agulli/atlas-agents

    Design, build, or debug data processing pipelines. An agent skill from agulli/atlas-agents.

    578 GitHub stars~714 tokensUpdated 2 mo ago
    Auto-check passed
  • Database Migration

    agulli/atlas-agents

    Safely run database schema migrations. An agent skill from agulli/atlas-agents.

    578 GitHub stars~702 tokensUpdated 2 mo ago
    Auto-check passed
  • Deploy Checklist

    agulli/atlas-agents

    Execute a structured deployment to staging or production. An agent skill from agulli/atlas-agents.

    578 GitHub stars~756 tokensUpdated 2 mo ago
    Auto-check passed
  • Documentation Writer

    agulli/atlas-agents

    Write or update technical documentation for code, APIs, or systems.

    578 GitHub stars~639 tokensUpdated 2 mo ago
    Auto-check passed
  • Performance Profiling

    agulli/atlas-agents

    Profile and optimize application performance. An agent skill from agulli/atlas-agents.

    578 GitHub stars~804 tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Git Commit

What does Git Commit do?

Create well-structured git commits with conventional commit messages. Git Commit is an agent skill from agulli/atlas-agents. Create well-structured git commits with conventional commit messages.

When should I use Git Commit?

Git Commit fits situations like: asked to commit changes; prepare a commit; stage and push code.

How do I install Git Commit in Claude Code?

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

How do I install Git Commit in Codex?

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

Can I use Git 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 agulli/atlas-agents --skill git-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/git-commit, .gemini/skills/git-commit, .github/skills/git-commit and .opencode/skills/git-commit in your project.

What does Git Commit need to run?

Going by SKILL.md and its folder, Git Commit needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash(git:*). Compatibility (from SKILL.md): Requires git.

Does Git 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 Git Commit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Git Commit use?

Git Commit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Commit use?

About 463 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 Git Commit?

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

agulli (a GitHub user) maintains it in agulli/atlas-agents, which has 578 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 17, 2026.

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