Standardizes git commit messages by analyzing changes and enforcing Conventional Commit formatting.

Install

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

Installs to .claude/skills/commit-rubentalstra

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.

Stage and commit the current changes as a single Conventional Commit that passes this repo's commit-msg rules. Use when the user asks to commit work in OpenWorkspace.
166 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Stage intended files for commit
  • Compose Conventional Commit messages
  • Validate commit messages against `commit-msg` hooks
  • Show the last commit details
  • Prevent commits on `main`/`master` branches
  • Add a body or breaking change footer to commits

How it works

This skill stages current changes and composes a Conventional Commit message based on predefined types and scopes. It then executes the commit, validating the message against local `commit-msg` hooks.

Inputs & outputs

You give it
Current changes in OpenWorkspace
You get back
A single Conventional Commit with a validated message

When to use commit

  • Committing finished work
  • Formatting commit messages
  • Verifying commit message conventions

About this skill

Create one Conventional Commit for the current change set in OpenWorkspace.

Steps

  1. Run git status and git diff --staged (and git diff for unstaged) to see exactly what will be committed. If nothing is staged, stage the intended files with git add — confirm the set is coherent and unrelated changes are left out.
  2. Confirm you are not on main/master. If you are, stop and tell the user to branch first (git checkout -b <type>/<topic>) — the hooks will reject a commit on main anyway.
  3. Compose the message:
    • type(scope): subject — type ∈ feat fix docs style refactor perf test build ci chore.
    • scope = the crate or app touched (domain db auth floorplan crypto i18n notify jobs ui config observability web worker app frontend server) or a cross-cutting scope (ci dev deps release).
    • subject: imperative mood, ≤50 chars, no trailing period.
    • Add a body only when the why isn't obvious from the subject. Use a BREAKING CHANGE: footer or ! after the scope for breaking changes (pre-V1: a breaking change bumps MINOR).
    • Never add an assistant/AI mention or any co-author/"generated with" trailer — commits are authored by the human only.
  4. Commit with git commit -m "..." (and -m again for a body). The local commit-msg hook validates the result; if it rejects, read the message and fix it rather than bypassing.
  5. Show the user the final git log -1 --stat.

Do not push or open a PR unless explicitly asked.

When not to use it

  • When pushing commits to a remote repository
  • When opening a pull request
  • When the user explicitly asks to bypass commit hooks

Limitations

  • The skill does not push commits
  • The skill does not open pull requests
  • The skill prevents committing directly to `main`/`master`

How it compares

This skill enforces Conventional Commit standards and validates messages automatically, unlike manually crafting and committing messages.

Compared to similar skills

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

SkillInstallsUpdatedSafetyDifficulty
commit (this skill)01moReviewBeginner
resolve-conflicts818moReviewIntermediate
dependency-upgrade265moReviewIntermediate
openspec-onboard106moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry