Skip to content
Agentmart
Submit a tool

git-conventional-commit

Create clean git commits using the Conventional Commits format (type(scope): summary).

Skill by nibzard

IndexedMIT★ 5
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/nibzard-git-conventional-commit

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Create clean git commits using the Conventional Commits format (type(scope): summary). Use when Codex needs to stage changes, craft commit messages, and record completed work in a Git repository.

Use cases: agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/git-conventional-commit

What's inside

Skill name
git-conventional-commit
Description
Create clean git commits using the Conventional Commits format (type(scope): summary). Use when Codex needs to stage changes, craft commit messages, and record completed work in a Git repository.
License
MIT
Instructions
22 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Git Conventional Commit

## Overview

Create one conventional commit per completed task while keeping the working tree clean and history stable.

## Workflow

1. Review changes with `git status` and `git diff`.
2. Stage only the changes related to the task (use `git add -A` or selective adds).
3. Compose a Conventional Commit message: `type(scope): summary`.
   - Types: feat, fix, refactor, docs, test, chore, build, ci, perf, style.
   - Use imperative mood and keep the summary under 72 characters.
4. Commit once per task. Do not amend, rebase, or rewrite history.
5. If there are no changes to commit, skip the commit and report why.

## Notes

- Avoid touching unrelated changes in a dirty working tree.
- Prefer a specific scope (folder or subsystem) when it clarifies intent.

From nibzard/looper-go, MIT.

More from nibzard/looper-go

Signals

Stars
5
Forks
0
Open issues
1
Last commit (this folder)
Jan 21, 2026 (9 months ago)
Last release
Jan 25, 2026 (9 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/nibzard/looper-go
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from nibzard

Cite this page

git-conventional-commit skill. Agent Mart. https://agentmart.dev/skills/nibzard-git-conventional-commit (last updated 2026-10-24)