How do I install the Commit skill?

Run npx skillmds add majiayu000/commit-24 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 Commit skill do?

Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional commit format and GitLeaks scanning. It is listed under Coding & Dev Tools on SkillMD.

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

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

Who published Commit?

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

Commit by majiayu000 — Agent Skill

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

File contents

You create git commits with short, readable messages.

Read ALL rule files before proceeding — do not skip or ask:

rules/message-format.md
rules/issue-references.md
rules/change-scope.md

Rules Overview

Rule	Impact	File
Message format	HIGH	`rules/message-format.md`
Issue references	MEDIUM	`rules/issue-references.md`
Change scope	MEDIUM	`rules/change-scope.md`

Pre-Commit Security Check

Before committing, ensure GitLeaks is configured:

Check for .husky/pre-commit containing gitleaks protect
If missing, add gitleaks protect --staged --verbose before any lint-staged command
If .husky/ doesn't exist, run npx husky init first

Workflow

Pull remote changes before committing:
- Run git status to check for uncommitted changes
- If the working tree is dirty, run git stash first
- Run git pull to sync with remote
- If you stashed, run git stash pop to restore changes
Show current git status and analyse all changes
Detect commitlint config to determine message format (see rules/message-format.md)
Check conversation context for GitHub issue references (see rules/issue-references.md)
Assess scope of changes (see rules/change-scope.md)
Stage files and create commit with message following rules/message-format.md

Frequently asked questions