Agent skill

Git Commit

A skill your agent uses when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

Apache-2.0Auto-check: notesDevelopment

Install Git Commit

skills CLI

$ npx skills add 21pounder/terminalAgent --skill git-commit -a claude-code

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

GitHub CLI

$ gh skill install 21pounder/terminalAgent 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/21pounder/terminalAgent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/deepresearch/.claude/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/

Paste into Claude Code

Install the "git-commit" agent skill from https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit into .claude/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add 21pounder/terminalAgent --skill git-commit -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install 21pounder/terminalAgent git-commit --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/21pounder/terminalAgent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/deepresearch/.claude/skills/git-commit .agents/skills/git-commit && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "git-commit" agent skill from https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit into .agents/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add 21pounder/terminalAgent --skill git-commit -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install 21pounder/terminalAgent git-commit --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/21pounder/terminalAgent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/deepresearch/.claude/skills/git-commit .cursor/skills/git-commit && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "git-commit" agent skill from https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit into .cursor/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/21pounder/terminalAgent.git --path deepresearch/.claude/skills/git-commit

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add 21pounder/terminalAgent --skill git-commit -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install 21pounder/terminalAgent git-commit --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/21pounder/terminalAgent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/deepresearch/.claude/skills/git-commit .gemini/skills/git-commit && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "git-commit" agent skill from https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit into .gemini/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install 21pounder/terminalAgent git-commit

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add 21pounder/terminalAgent --skill git-commit -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/21pounder/terminalAgent.git skills-src && mkdir -p .github/skills && cp -r skills-src/deepresearch/.claude/skills/git-commit .github/skills/git-commit && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "git-commit" agent skill from https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit into .github/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add 21pounder/terminalAgent --skill git-commit -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install 21pounder/terminalAgent git-commit --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/21pounder/terminalAgent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/deepresearch/.claude/skills/git-commit .opencode/skills/git-commit && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "git-commit" agent skill from https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit into .opencode/skills/git-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: git-commit
GitHub stars: 120
Used in: 1 other repo
Token cost: ~642 tokens
SKILL.md length: 268 words
Files: 1
Skills in repo: 4
Repo updated: May 28, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

Works in 4 steps: Status Check → Analysis → Commit Creation → …
User asks to commit changes
SKILL.md covers Parameters, When to Use, Methodology and Guidelines, plus 1 more section
Calls git

What it does

Git Commit is an agent skill from 21pounder/terminalAgent. Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

Its SKILL.md is about 640 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: A powerful terminal coding agent based on Claude Agent SDK. Better then Claude Code when start up a new project, or u have no idea. Just try it. The licence is Apache-2.0.

When your agent uses it

User asks to commit changes
Create a commit
Stage and commit
Wants help with git commit workflow

Example prompts

“commit changes”
“create a commit”
“stage and commit”
“/git-commit”

Requirements

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

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Status Check
Analysis
Commit Creation
Output

What it can do on your machine

Read from SKILL.md and the folder at commit 989b029. 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:
- Read
- Bash
- Glob
- Grep
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

Git Commit loads about 642 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 268 words of instructions outside code blocks.

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

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

- Don't commit sensitive files (.env, credentials, etc.)

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Bash, Glob, Grep
```

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 21pounder/terminalAgent at commit 989b029, republished under its Apache-2.0 licence (© 21pounder). 268 words, ~642 tokens.

Download SKILL.mdSave it as .claude/skills/git-commit/SKILL.md (or your agent's skills folder).

name: git-commit
description: Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.
allowed-tools: Read, Bash, Glob, Grep
version: 1.0.0

Git Commit

Create well-structured git commits with conventional commit messages based on staged changes.

Parameters

json

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "description": "Optional commit message override"
    },
    "type": {
      "type": "string",
      "enum": ["feat", "fix", "docs", "style", "refactor", "test", "chore"],
      "description": "Conventional commit type",
      "default": "auto"
    },
    "scope": {
      "type": "string",
      "description": "Optional scope for the commit"
    }
  }
}

When to Use

User asks to "commit" changes
User wants to "save" their work to git
User asks for help with commit messages
User wants to stage and commit files

Methodology

Phase 1: Status Check

Run git status to see current state
Run git diff --staged to see staged changes
Run git diff to see unstaged changes
Check recent commit history for message style

Phase 2: Analysis

Categorize Changes: Identify what changed (new files, modifications, deletions)
Determine Type: Is this a feature, fix, refactor, etc.?
Identify Scope: What component/module is affected?
Summarize Purpose: What does this change accomplish?

Phase 3: Commit Creation

Stage relevant files if not already staged
Generate conventional commit message
Execute the commit
Verify success with git status

Phase 4: Output

Report:

What was committed
The commit message used
The new commit hash

Guidelines

Follow Conventional Commits format: type(scope): description
Keep subject line under 72 characters
Use imperative mood ("Add feature" not "Added feature")
Don't commit sensitive files (.env, credentials, etc.)
Don't use --force or --amend unless explicitly requested
Include meaningful description of WHY, not just WHAT

Examples

Example 1: Auto Commit

User Input: "Commit my changes"

Expected Behavior:

Run git status and git diff to understand changes
Analyze the nature of changes
Generate appropriate commit message
Stage files if needed
Create commit and report success

Example 2: Specific Type

User Input: "创建一个 fix 类型的 commit"

Expected Behavior:

检查当前的改动
确认这些改动符合 "fix" 类型
生成格式为 fix(scope): 描述 的提交信息
执行提交并报告结果

Files

Just SKILL.md in deepresearch/.claude/skills/git-commit of 21pounder/terminalAgent.

Open the folder on GitHubat commit 989b029

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in 21pounder/terminalAgent, which our catalogue first saw on October 7, 2026.

aiskillstore/marketplaceskills/21pounder/git-commit

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Git Commit this skill21pounder/terminalAgent	120	1 repos	~642	Automated safety check: Notes	Apache-2.0	4 mo ago
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Git Workflow and Versioningaddyosmani/agent-skills	102k	2 repos	~3.5k	Automated safety check: Notes	MIT	4 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	yesterday
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	yesterday

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.
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 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 yesterday
DevelopmentAuto-check passed

Questions about Git Commit

What does Git Commit do?

A skill your agent uses when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow. Git Commit is an agent skill from 21pounder/terminalAgent. Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

When should I use Git Commit?

Git Commit fits situations like: user asks to commit changes; create a commit; stage and commit; wants help with git commit workflow.

How do I install Git Commit in Claude Code?

Run `npx skills add 21pounder/terminalAgent --skill git-commit -a claude-code`. Or copy the skill folder (deepresearch/.claude/skills/git-commit in 21pounder/terminalAgent) 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 21pounder/terminalAgent --skill git-commit -a codex`. Or copy the skill folder (deepresearch/.claude/skills/git-commit in 21pounder/terminalAgent) 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 21pounder/terminalAgent --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: Read, Bash, Glob, Grep.

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; 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 Git Commit use?

Git Commit is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Commit use?

About 642 tokens (SKILL.md is roughly 2.6k 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?

21pounder (a GitHub user) maintains it in 21pounder/terminalAgent, which has 120 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on May 28, 2026.

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

Install Git Commit

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Git Commit

Parameters

When to Use

Methodology

Phase 1: Status Check

Phase 2: Analysis

Phase 3: Commit Creation

Phase 4: Output

Guidelines

Examples

Example 1: Auto Commit

Example 2: Specific Type

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from 21pounder/terminalAgent

Related

Questions about Git Commit