How do I install the Committing skill?

Run npx skillmds add majiayu000/committing 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 Committing skill do?

Creates well-structured git commits following conventional commit format. Use when committing changes, preparing commits, or when asked to commit code. It is listed under Coding & Dev Tools on SkillMD.

Is Committing safe to use?

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

Which AI agents work with Committing?

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 Committing free to use?

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

Who published Committing?

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

Committing by majiayu000 — Agent Skill

Name: Committing
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Git Committing

Commit Message Format

<type>(<scope>): <subject>

[optional body]

[optional footer]

Types

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting, no code change
`refactor`	Code change without fix/feature
`perf`	Performance improvement
`test`	Adding or fixing tests
`chore`	Build, CI, tooling changes

Rules

Subject line: Under 50 characters, imperative mood ("add" not "added")
Body: Wrap at 72 characters, explain "why" not "what"
Scope: Optional, indicates affected area (e.g., parser, api, ui)
Breaking changes: Add ! after type or BREAKING CHANGE: in footer

Workflow

Run git status to see changes
Run git diff to review modifications
Check recent commits with git log --oneline -5 for style consistency
Stage specific files (avoid git add -A)

Write commit message using HEREDOC:

git commit -m "$(cat <<'EOF'
type(scope): subject

Body explaining why this change was made.
EOF
)"

Verify with git status

Safety

Never commit secrets, credentials, or .env files
Never use --no-verify unless explicitly requested
Never amend commits that have been pushed
Create NEW commits after hook failures, don't amend

Frequently asked questions