Draft commit message

Skill geekswamp/agent-skills/skills/draft-commit-message

A curated set of reusable Codex skills for common engineering tasks.

Install

npx -y skills add geekswamp/agent-skills --skill draft-commit-message

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft a Conventional Commit message from current repo changes. Use this skill whenever the user asks for help writing, drafting, or formatting a commit message, especially when they refer to their git diff, staged changes, or recent work. Trigger it automatically when a user says they are "ready to commit," "finished a feature," or needs a "summary of what I did" for source control. This skill is optimized to follow Conventional Commits (type, scope, and imperative mood).

SKILL.md

1.9 KB, as published. Nobody here has run it

Draft a conventional commit message that matches the change summary provided by the user.

Requirements

Use the Conventional Commits format: type(scope): summary.
Use the imperative mood in the summary (for example, feat, fix, refactor).
The supported types are bump, feat, fix, docs, refactor, test, ci, chore, perf, and revert.
The entire first line (including type and scope) must not exceed 72 characters.
Do not wrap the summary line.
If there are breaking changes, include a BREAKING CHANGE: footer.
Always use English.

Script

Alway run git-diff.sh script before generating a commit message.
Run:
- bash scripts/git-diff.sh
- Optional scoped analysis: bash scripts/git-diff.sh <path>
Use the script output as the primary source of truth for determining the commit type and summary.
The script shows both staged and unstaged status, diff stats, full diffs, and untracked files.

Output Contract

Return commit message text only (no explanation) unless user asks for reasoning.
Follow the exact output format in REFERENCE.md:
- Subject: type(scope): summary (<=72 chars)
- Optional body: concise bullet points
- Optional footer: BREAKING CHANGE: ...