smithery.ai

commit-format

Write concise commit messages focused on the why

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 Declared

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Compatibilityopencode
Declared agents opencode
More metadata
audience
developers
scope
git

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 553 B
  • docs SUMMARY.md 69 B

History

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

SKILL.md

What I do

  • Suggest a 1-line subject and a short body (when needed)
  • Emphasize intent (why) over implementation detail (what)

Guidelines

  • Use imperative mood: "add", "fix", "refactor"
  • Keep subject under ~72 chars when possible
  • Mention user impact or bug context in the body

When to ask questions

  • If the change spans multiple concerns, ask how to split commits