Generate commit msg

Skill itsjavi/skills/skills/generate-commit-msg

Coding agent skills to help projects adopt spec-driven development with durable product memory documents

Install

npx -y skills add itsjavi/skills --skill generate-commit-msg

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

One thing to look at

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

Generate a Conventional Commit message for the repository's current staged changes. Use when the user asks for a commit message, commit title, git commit message, or conventional commit summary based on staged changes. The output must be only the message as plaintext code, with no explanation or follow-up text.

SKILL.md

2.2 KB, as published. Nobody here has run it

Generate Commit Message

Create a commit message for the repository's current staged changes.

Workflow

Inspect the git index without changing it:

git status --short
git diff --cached --stat
git diff --cached

Base the message only on staged changes. Ignore unstaged and untracked changes except to avoid mixing them into the staged summary.
If there are no staged changes, output a plaintext code block containing exactly:
```
chore: no staged changes
```

Message Rules

Use Conventional Commit format:

<type>(optional-scope): <imperative summary>

Allowed types: feat, fix, docs, chore, refactor, test, build, ci.
Put the most important staged change first.
If there is room on the same line, include minor staged changes after the primary change.
Keep the subject concise and readable. Prefer one line unless extra context is genuinely needed.
Use imperative mood: add, fix, update, remove, refactor, not added, fixes, or updated.
Do not mention file paths unless they are the clearest useful scope.

Optional Body

Add body text only when it is important and genuinely needed for context, such as a breaking behavior change, migration note, or significant secondary changes that do not fit in the subject.

When a body is needed:

Keep it short.
Use markdown list bullets instead of paragraphs.
Include only important staged changes.

Example:

feat(auth): add passkey enrollment and tighten session renewal

- Requires a new WebAuthn origin setting in production.
- Moves legacy session cleanup behind the renewal path.

Output Contract

Output nothing except one plaintext code block containing the exact commit message.

Do not add explanations, labels, summaries, caveats, follow-up questions, or text outside the code block.