agentsclimarketplace

Give me a commit message

Skill vthinkdeveloper/vthink-agent-toolkit/skills/give-me-a-commit-message

Suggest a Conventional Commits message based on current staged and unstaged changes. Does not commit — just outputs the message to copy. Extracts ticket ID from branch name if present. Use when you want a commit message suggestion without committing.From its SKILL.md

Install
npx -y skills add vthinkdeveloper/vthink-agent-toolkit --skill give-me-a-commit-message

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

  • 2 stars2 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.

SKILL.md

1.7 KB, as published. Nobody here has run it

Suggest Commit Message

Analyze the current changes and suggest a commit message. Do NOT commit or push.

Workflow

Step 1: Gather Context

Run these in parallel:

  • git diff --staged — staged changes
  • git diff — unstaged changes
  • git status — overview of modified/new/deleted files
  • git branch --show-current — current branch name
  • git log --oneline -5 — recent commits for style reference

Step 2: Extract Ticket ID

From the branch name, extract any ticket ID pattern (e.g., PROJ-1234, FEAT-567, BUG-42).

  • Pattern: uppercase letters + hyphen + numbers (e.g., [A-Z]+-\d+)
  • If found, prefix the commit message with it

Step 3: Generate Message

Write a commit message following these rules:

  • If a ticket ID was found, format as: TICKET-ID: Description
  • Match the style of recent commits in the repo
  • First line: concise summary under 72 characters
  • If the change is non-trivial, add a blank line then a short body explaining the "why"
  • Focus on why the change was made, not what changed (the diff shows that)

Step 4: Output

Present the suggested message like this:

Suggested commit message:

TICKET-ID: Short description of the change

Optional body explaining why, if needed.

Then say: "Copy and use with git commit -m \"...\", or ask me to refine it."

Do NOT run git commit, git add, or git push. Only suggest.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.