Analyze staged git changes and generate commit message options with title and body
From arribanpx claudepluginhub nmoinvaz/speedy-gonzales --plugin arribaThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Each commit message has a title and body, separated by a blank line. Match the existing commit formatting in the repository first; use these defaults where the repo has no clear convention.
Title:
git log --oneline and avoids truncation)Body:
Voice: Read and follow the voice guidelines in skills/code-voice/SKILL.md
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:
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>"