Agent skill

Git Commit

Git commit workflow in a worktree with Python linting, formatting, and testing.

Apache-2.0Auto-check: notesDevelopment

Install Git Commit

skills CLI

$ npx skills add nex-agi/NexRL --skill git-commit -a claude-code

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

GitHub CLI

$ gh skill install nex-agi/NexRL 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/nex-agi/NexRL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.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/nex-agi/NexRL/tree/main/.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/nex-agi/NexRL/tree/main/.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 nex-agi/NexRL --skill git-commit -a codex

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

GitHub CLI

$ gh skill install nex-agi/NexRL 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/nex-agi/NexRL.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.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/nex-agi/NexRL/tree/main/.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 nex-agi/NexRL --skill git-commit -a cursor

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

GitHub CLI

$ gh skill install nex-agi/NexRL 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/nex-agi/NexRL.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.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/nex-agi/NexRL/tree/main/.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/nex-agi/NexRL.git --path .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 nex-agi/NexRL --skill git-commit -a gemini-cli

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

GitHub CLI

$ gh skill install nex-agi/NexRL 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/nex-agi/NexRL.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.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/nex-agi/NexRL/tree/main/.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 nex-agi/NexRL 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 nex-agi/NexRL --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/nex-agi/NexRL.git skills-src && mkdir -p .github/skills && cp -r skills-src/.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/nex-agi/NexRL/tree/main/.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 nex-agi/NexRL --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 nex-agi/NexRL 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/nex-agi/NexRL.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.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/nex-agi/NexRL/tree/main/.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: 119
Token cost: ~380 tokens
SKILL.md length: 75 words
Files: 1
Skills in repo: 6
Repo updated: Sep 17, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Git commit workflow in a worktree with Python linting, formatting, and testing.

Works in 7 steps: Analyze Changes → Format & Lint → Run Tests → …
Tasks that involve Commit messages
SKILL.md covers Prerequisites and Workflow
Calls git and python

What it does

Git Commit is an agent skill from nex-agi/NexRL. Git commit workflow in a worktree with Python linting, formatting, and testing.

Its SKILL.md is about 380 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, Linting and formatting and Git worktrees. It works with Python. The repository describes itself as: NexRL is an ultra-loosely-coupled LLM post-training framework. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Commit messages
Tasks that involve Linting and formatting
Tasks that involve Git worktrees

Example prompts

“/git-commit”

Requirements

Python 3

Workflow steps

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

Analyze Changes
Format & Lint
Run Tests
Review (use code-review skill)
Stage Changes
Commit
Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 53dcdec. 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
- python
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 380 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 75 words of instructions outside code blocks.

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

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

**Never stage:** `__pycache__/`, `.env`, `*.egg-info/`, build artifacts, coverage files

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 nex-agi/NexRL at commit 53dcdec, republished under its Apache-2.0 licence (© nex-agi). 75 words, ~380 tokens.

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

name: git-commit
description: Git commit workflow in a worktree with Python linting, formatting, and testing.

Git Commit Workflow (Worktree-Aware)

Prerequisites

Verify you're in a worktree (not main clone):

bash

git rev-parse --show-toplevel
git worktree list

Workflow

Step 1: Analyze Changes

bash

git diff --name-only
git diff --cached --name-only

Step 2: Format & Lint

bash

# Format changed Python files
python -m black <changed_python_files>
python -m isort <changed_python_files>

# Fix license headers
python tests/lint/fix_license_header.py <changed_files>

# Lint
python -m pylint <changed_python_files> --rcfile=.pylintrc -rn -sn
python -m mypy <changed_python_files> --ignore-missing-imports

Step 3: Run Tests

bash

python -m pytest tests/ -v --tb=short

Step 4: Review (use code-review skill)

Follow .ai-instructions/code-review/generic.md checklist.

Step 5: Stage Changes

bash

git add path/to/changed/files
git diff --staged  # Final review

Never stage: __pycache__/, .env, *.egg-info/, build artifacts, coverage files

Step 6: Commit

Format: type(scope): description (72 chars max)

Types: feat, fix, refactor, test, docs, style, chore, perf

bash

git commit -m "type(scope): description

Detailed explanation if needed.

Fixes #ISSUE_NUMBER"

No AI co-author lines. (per .ai-instructions/developing/commit-guidelines.md)

Step 7: Verify

bash

git show HEAD --name-only
git log -1

Files

Just SKILL.md in .claude/skills/git-commit of nex-agi/NexRL.

Open the folder on GitHubat commit 53dcdec

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 skillnex-agi/NexRL	119	—	~380	Automated safety check: Notes	Apache-2.0	20 days ago
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	yesterday
Git HooksProrise-cool/Claude-Code-Multi-Agent	305	—	~3.6k	Automated safety check: Notes	None	21 days ago
Python NethsecurityNethServer/nethsecurity	191	—	~2k	Automated safety check: Pass	Custom licence	yesterday
Git PR Workflowandymai/brepjs	114	—	~2.9k	Automated safety check: Pass	Apache-2.0	yesterday
Kedro Babysitkedro-org/kedro	11k	—	~4k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

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
Git Hooks
Prorise-cool/Claude-Code-Multi-Agent
Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.
305 GitHub stars~3.6k tokensUpdated 21 days ago
DevelopmentAuto-check: notes
Python Nethsecurity
NethServer/nethsecurity
Write or modify Python scripts for NethSecurity packages. An agent skill from NethServer/nethsecurity.
191 GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Git PR Workflow
andymai/brepjs
This skill should be used when committing, pushing, branching, or merging in the brepjs repository — when a task involves "pre-commit hook failed" (which tier ran, how to bypass), "commit rejected…
114 GitHub stars~2.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
11k GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed
Commitizen
commitizen-tools/commitizen
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
3.5k GitHub stars~839 tokensUpdated today
DevelopmentAuto-check passed

Questions about Git Commit

What does Git Commit do?

Git commit workflow in a worktree with Python linting, formatting, and testing. Git Commit is an agent skill from nex-agi/NexRL. Git commit workflow in a worktree with Python linting, formatting, and testing.

When should I use Git Commit?

Git Commit fits situations like: tasks that involve Commit messages; tasks that involve Linting and formatting; tasks that involve Git worktrees.

How do I install Git Commit in Claude Code?

Run `npx skills add nex-agi/NexRL --skill git-commit -a claude-code`. Or copy the skill folder (.claude/skills/git-commit in nex-agi/NexRL) 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 nex-agi/NexRL --skill git-commit -a codex`. Or copy the skill folder (.claude/skills/git-commit in nex-agi/NexRL) 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 nex-agi/NexRL --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 and python). Our summary lists: Python 3.

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 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 380 tokens (SKILL.md is roughly 1.5k 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: Saleor Commit Workflow (saleor/saleor, 23k stars), Git Hooks (Prorise-cool/Claude-Code-Multi-Agent, 305 stars), Python Nethsecurity (NethServer/nethsecurity, 191 stars) and Git PR Workflow (andymai/brepjs, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Commit?

nex-agi (a GitHub organization) maintains it in nex-agi/NexRL, which has 119 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 17, 2026.

Source: nex-agi/NexRL 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 Workflow (Worktree-Aware)

Prerequisites

Workflow

Step 1: Analyze Changes

Step 2: Format & Lint

Step 3: Run Tests

Step 4: Review (use code-review skill)

Step 5: Stage Changes

Step 6: Commit

Step 7: Verify

Files

Compare with similar skills

Similar skills

More from nex-agi/NexRL

Related

Questions about Git Commit