Git Commit

Generates storytelling-focused Conventional Commits messages with Jira context, then commits and pushes changes.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill git-commit-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git Commit
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/0xMassi-claude-skills/git-commit
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill git-commit-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing meaningful commit messages is often rushed or skipped, leaving future developers without context about why changes were made. This Skill generates detailed Conventional Commits messages that capture the what, why, and problem solved, enriched with Jira ticket context. ## Core Features & Use Cases - Storytelling Commit Messages: Produces structured messages covering why the change was needed, what changed, and what problem it solves, following Conventional Commits types (feat, fix, refactor, etc.). - Jira Integration: Parses the branch name for ticket IDs (e.g., PROJ-123) and fetches ticket details via the Zapier MCP server to add business context and a Refs footer. - Human-in-the-Loop Context: Asks the user why the change was made with multiple-choice options inferred from the actual diff, then commits and pushes only after explicit confirmation. - Use Case: After finishing a bug fix on branch feature/AGP-582-timeout, say "commit this" and receive a complete message referencing the Jira ticket, your stated motivation, and a technical summary of the staged diff. ## Quick Start Say "commit my changes" after staging your files and confirm the generated commit message when prompted.

Frequently Asked Questions about Git Commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good Conventional Commits message?▼

Use a type prefix like feat, fix, or refactor with a concise subject, then add body sections explaining why the change was needed, what changed technically, and what problem it solves. This Skill generates that structure automatically from your staged diff.

How do I include Jira ticket context in git commit messages?▼

Name your branch with the ticket ID, such as feature/PROJ-123-description. The Skill parses the branch name, fetches the issue via the Zapier MCP Jira integration, and appends a Refs: PROJ-123 footer to the commit message.

Does this Skill commit and push automatically without confirmation?▼

No. The git commit and git push commands are deliberately excluded from the allowed-tools list, so you are always prompted for approval before either command executes. It also never runs git add -A or git add .

What git commands does the commit workflow use?▼

It runs git status, git diff --staged, git log --oneline -5, and git branch --show-current to gather context. Commits use a heredoc format to preserve multi-line message formatting.

Why does the Skill ask why I made the changes?▼

The diff shows what changed but not the motivation behind it. The Skill uses AskUserQuestion with options inferred from your actual code changes so the commit message captures intent for future code archeology.