Commit msg

Claude commands that speed up everyday dev workflows

Install

npx -y skills add nmoinvaz/speedy-gonzales --skill commit-msg

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.
3 stars3 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.

Copied from the file, not written here

Analyze staged git changes and generate commit message options with title and body

1.0 KB, 208 tokens by cl100k_base, as published. Nobody here has run it

Get the staged diff for analysis:
```
git diff --cached
```
Check previous commit message format in the repository:
```
git log --oneline -10
```
Search staged changes for ticket IDs (patterns like PROJ-123, D4T-123, etc.)
Generate 3 distinct commit message options following the format above. Each option should use a different verb and framing — not rephrase the same sentence.
Follow these guidelines:
- Match the format used in previous commits in the repository
- If a ticket ID was found, include it in the title (typically as a prefix)
- Do not add Claude as a co-author in the commit message
Present the options to the user for selection using AskUserQuestion
Create the commit with the selected title and body:
```
git commit -m "<title>" -m "<body>"
```