Stages files and creates git commits using conventional message standards based on repo history.

Install

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

Installs to .claude/skills/commit-cosmevalera

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 relevant changes and create a git commit with a conventional-style message. Only runs when the user explicitly invokes /commit.
133 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Identify relevant files for staging
  • Draft a concise commit message based on project style
  • Stage selected files by name
  • Confirm successful staging with git status
  • Avoid committing secret files

How it works

The skill analyzes git status and diff to identify changes, drafts a commit message following project style, and stages files by name while avoiding secrets.

Inputs & outputs

You give it
Current git changes (staged and unstaged) and an optional commit message hint
You get back
A git commit with selected files staged and a conventional-style message

When to use commit

  • Stage selected files for a commit
  • Generate conventional commit messages
  • Review changes before finalizing a commit

About this skill

/commit

Create a git commit for the current changes.

Steps

  1. Run in parallel:
    • git status (no -uall)
    • git diff (staged + unstaged)
    • git log -n 10 --oneline to match the repo's commit style
  2. Review what would be committed:
    • Skip files that likely hold secrets (.env, credentials, keys).
    • Do not blanket-add with git add -A/git add . — stage files by name.
    • If $ARGUMENTS is non-empty, treat it as the commit message (or message hint) from the user.
  3. Draft a concise 1–2 sentence commit message focused on the why. Follow this repo's existing style from git log (the project uses short imperative subjects like "Improve SEO", "Add CLAUDE.md file").
  4. Stage the intended files:
  5. Run git status after to confirm success.
  6. Do not push. Do not amend. If a pre-commit hook fails, fix the root cause and create a new commit.

Guardrails

  • Never use --no-verify, --amend, or force flags.
  • Never commit .env, credentials, or large binaries — warn the user instead.
  • If there is nothing to commit, say so and stop — do not create empty commits.
  • Do not add a Co-Authored-By: Claude trailer. Commits should look authored solely by the user.

When not to use it

  • When there is nothing to commit
  • When the user wants to amend an existing commit
  • When the user wants to push changes

Limitations

  • Does not push commits to a remote repository
  • Does not amend existing commits
  • Does not use `--no-verify` or force flags

How it compares

This skill automates the selection of relevant files and the drafting of a conventional commit message, unlike a manual process that requires explicit file selection and message composition.

Compared to similar skills

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

SkillInstallsUpdatedSafetyDifficulty
commit (this skill)03moReviewBeginner
run-nx-generator53moReviewIntermediate
git-commit116moReviewBeginner
morph-search97moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry