Skip to main content
skill CX Codex

commit · justxor — Claude Code skill for Conventional Commits

This skill reviews your working changes and creates a git commit in Conventional Commits format. Use it when you want an agent to make a commit that follows the repository’s message style.

MIT ★ 353 updated 2026-10-01

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add justxor/claude-code-pro-course --skill commit -a claude-code
Open on GitHub

What commit does

The skill checks the working tree and diffs, including staged changes, then reads recent commit messages to follow the repository’s conventions. When changes belong to separate concerns, it suggests splitting them into multiple commits. It then stages the changes and writes a commit with a type such as feat, fix, or docs.

A commit message uses a type, an optional scope, and a brief imperative summary; it can include a reason when the change is not self-explanatory. The skill excludes .env, secrets, temporary files, and generated files. It needs git changes in the repository and is limited to git status, git diff, git add, git commit, and git log. It displays the latest commit when done.

What it helps with

  • commit the current working changes
  • write messages in Conventional Commits format
  • match commit wording to repository history
  • split unrelated changes into separate commits
  • keep secrets and generated files out of a commit

Example prompts for the agent

  • Commit my current changes using Conventional Commits.
  • Review the diff and create a suitable git commit.
  • Separate unrelated changes into commits, then commit them.

How to install commit

1Skills CLI (Vercel)

npx skills add justxor/claude-code-pro-course --skill commit -a claude-code

2Manually: put the files in place

~/.claude/skills/commit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/commit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about commit

How do I install commit in Claude Code?

Run npx skills add justxor/claude-code-pro-course --skill commit -a claude-code. The skill file is at ~/.claude/skills/commit/SKILL.md.

What does the commit skill do?

It reviews the working changes and recent commit history, then creates a commit in Conventional Commits format. It keeps .env, secrets, temporary files, and generated files out of the commit.

Which commit types does commit support?

It supports feat, fix, refactor, test, docs, chore, perf, and ci. If the changes cover separate concerns, it suggests making multiple commits.

Source text

SKILL.md · MIT
---
name: commit
description: Создаёт git-коммит в формате Conventional Commits по текущим изменениям. Используй, когда просят закоммитить или сделать коммит.
allowed-tools: Bash(git status), Bash(git diff:*), Bash(git add:*), Bash(git commit:*), Bash(git log:*)
argument-hint: "[необязательное пояснение]"
---

# Commit

Контекст от пользователя: $ARGUMENTS

1. `git status` и `git diff` (+ `git diff --staged`) — пойми, что изменилось.
2. `git log --oneline -10` — посмотри стиль сообщений в репозитории.
3. Если изменения логически разные — предложи разбить на несколько коммитов.
4. Не добавляй в коммит `.env`, секреты, временные и сгенерированные файлы.
5. Сообщение:
   ```
   <type>(<scope>): <кратко, повелительное наклонение, до 72 символов>

   <зачем сделано изменение, если неочевидно>
   ```
   type: feat | fix | refactor | test | docs | chore | perf | ci
6. Сделай коммит и покажи `git log --oneline -1`.

© justxor · MIT · justxor/claude-code-pro-course

Similar skills

All skills for Git and GitHub →

commit by other authors comes first.

commit getsentry Drafts Sentry-style conventional commits with issue references and blocks direct commits to main. CX Codex +1 4,900installs commit NeoLabHQ Automates Git commits using conventional commit messages and matching emojis. It checks the active branch, runs pre-commit linters, and suggests splitting complex diffs into atomic commits. CX Codex +1 1,300installs commit parcadei This skill turns session changes into git commits, shows you the plan first, and keeps Claude's name out of the messages. Handy when an agent has piled up edits. CX Codex +1 505installs commit FradSer This skill creates atomic conventional commits through git-agent. Use it when a short intent should become a focused Git commit. CX Codex +1 121installs commit PaulRBerg Composes the commit message from prepared evidence and hands the commit, index reconciliation and push to ai-commit. CX Codex +1 347installs setup-pre-commit Matt Pocock The setup-pre-commit skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. CX Codex +1 489,289installs caveman-commit JuliusBrussee caveman-commit generates terse Conventional Commits messages focused strictly on intent. Ideal for keeping git history clean without boilerplate or AI signatures. CX Codex +1 441,600installs git-commit official github A GitHub Copilot skill that turns a working diff into a commit: it reads the changes, stages the related files, writes a Conventional Commits message and runs git commit. CX Codex +1 47,165installs conventional-commit official github A GitHub Copilot skill that builds commit messages in the Conventional Commits format. After you change files, it checks the diff and commits with a message assembled from an XML template. CX Codex +1 17,103installs commit-context rohitg00 The commit-context skill links a file, function, or line to the commit and agent session behind it. Use it when a code change needs its history and context. CX Codex +1 14,700installs commit-history rohitg00 commit-history lists git commits linked to agent sessions with optional filters for branch, repo, and limit. CX Codex +1 14,600installs

From the same set15

The whole set →
pr-description pr-description generates clear pull request titles and descriptions by inspecting branch commits and diffs against main. CX Codex +1 ★ 353repo stars architect The architect subagent examines a project before implementation, compares design options, and lays out a change plan. Use it to scope a feature or a major refactor. CX Codex ★ 353repo stars code-reviewer code-reviewer reads your diff, flags security holes, missing tests and edge cases, then returns a severity-sorted report with a file and line for each fix. CX Codex ★ 353repo stars write-tests write-tests generates unit tests for a chosen file or function while matching existing project patterns. It runs new checks and flags discovered bugs instead of bending assertions. CX Codex +1 ★ 353repo stars refactor Runs refactoring as a sequence of small, behavior-preserving steps. Use it when you ask the agent to split a module or remove duplication. CX Codex +1 ★ 353repo stars release-notes Generates release notes and CHANGELOG entries between Git tags or from the latest tag to HEAD using Conventional Commits. CX Codex +1 ★ 353repo stars onboard The onboard skill gives a new developer a guided introduction to a codebase, from its layout to its main workflows. Use it when someone needs to get oriented and find a first task. CX Codex +1 ★ 353repo stars code-review The code-review skill checks changes in the current branch against main and produces a report with notes on correctness, security, tests, and readability. CX Codex +1 ★ 353repo stars

Project sponsors

Companies that keep this analytics open