Standardizes git commit messages and scoping.

Install

mkdir -p .claude/skills/commit-hojinzs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16555" && unzip -o skill.zip -d .claude/skills/commit-hojinzs && rm skill.zip

Installs to .claude/skills/commit-hojinzs

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create clean, logically scoped commits that keep the repository in a shippable state.
85 charsno explicit “when” trigger
Beginner

Key capabilities

  • Commit changes in logical units
  • Ensure tests pass before committing
  • Format commits using Conventional Commit
  • Use specific types like feat, fix, refactor, test, docs, chore
  • Write descriptions in imperative mood with a 50-character limit

How it works

This skill guides the user to create commits that adhere to Conventional Commit format and specific content rules. It ensures each commit represents a single concern and passes tests.

Inputs & outputs

You give it
code changes
You get back
a formatted commit message

When to use commit

  • Committing changes
  • Scoping features and fixes
  • Maintaining commit history

About this skill

/commit — Clean Commit Workflow

Trigger

Use this skill when creating commits during implementation.

Rules

  • Commit in logical units — one concern per commit
  • Never commit a broken intermediate state (tests must pass)
  • Never commit temporary debug code or commented-out blocks
  • Run tests before every commit

Format

Use Conventional Commit format:

<type>(<scope>): <description>

[optional body — explain WHY, not WHAT, 72 chars/line]

[optional footer: Closes #N]

Types: feat, fix, refactor, test, docs, chore

Description: imperative mood, 50 chars max, no period at end

Examples

feat(auth): add OAuth2 token refresh
fix(api): handle null response from upstream
test(worker): add retry exhaustion coverage

When not to use it

  • When committing broken intermediate states
  • When committing temporary debug code
  • When committing commented-out blocks

Limitations

  • Requires running tests before every commit
  • Requires adherence to specific commit types
  • Requires descriptions to be 50 characters maximum

How it compares

This workflow provides explicit rules for commit content and format, unlike a manual approach that allows arbitrary commit messages.

Compared to similar skills

commit side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
commit (this skill)05moNo flagsBeginner
tmux203moReviewIntermediate
jira116moNo flagsBeginner
triaging-issues52moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry