How do I install the Git Commit skill?

Run npx skillmds@latest add nazozokc/git-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Git Commit skill do?

Rules for Git commits, pushes, and PR creation It is listed under Coding & Dev Tools on SkillMD.

Is Git Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit?

nazozokc (@nazozokc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit by nazozokc — Agent Skill

Name: Git Commit
Author: nazozokc

File contents

Git Operation Guidelines

When to Use

When committing files
When pushing to remote

Basic Rules

No Japanese in commits: English only
1 commit = 1 logical change: Do not mix multiple different changes
Meaningful granularity: Split large changes
Branch must always be AI-agent: Always commit and push to AI-agent
Code review before committing: See ../code-review/SKILL.md

Branch Strategy

Working branch: Always use AI-agent
PR target: Merge AI-agent → main
Branch creation: If AI-agent doesn't exist, create it first

Commit Message Format

<type>: <summary>

Type List

type	usage
`feat`	New feature
`fix`	Bug fix
`refactor`	Refactoring
`docs`	Documentation change
`chore`	Build/config change
`style`	Formatting/style change

Examples

feat: add neovim telescope config
fix: resolve fish greeting display bug
chore: update flake.lock
refactor: simplify home-manager modules

Notes

Run git status before committing to confirm changes
Auto-generated files should be committed separately
Never use --force variants before creating a PR

Frequently asked questions

Git Commit