smithery.ai

commit message

Commit staged or unstaged git changes with a clear, informative message (subject + body). Use when asked to commit work, finalize edits, or generate a commit message after changes are made.

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,109 B
  • docs SUMMARY.md 211 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

Commit Message

Overview

Create a clean git commit by staging the right changes and writing a concise subject with a useful body.

Workflow

  1. Check status with git status -sb. If the working tree is clean, report that nothing needs committing.
  2. Review diffs (git diff and git diff --staged) to understand what changed and why.
  3. Stage the intended changes. Prefer selective adds, but use git add -A if everything should be included.
  4. Write the commit message:

- Subject: imperative mood, <= 72 chars, summarize the main change. - Body: one blank line, then short paragraphs or bullets covering why the change was made, key details, and user impact. - Add a final Tests: line (e.g., Tests: not run or Tests: pytest).

  1. Commit with git commit -m "subject" -m "body".
  2. Confirm with git log -1 and report the commit hash and subject.