Git Commit

Name: Git Commit
Availability: InStock
Author: Zapier

Generate Conventional Commits with Jira context and push changes.

373|53|Updated Sep 11, 2025

Ready to run

npx skills add https://github.com/zapier/zapier-mcp --skill git-commit-zapier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Git Commit
Source: https://github.com/zapier/zapier-mcp/tree/main/dist/plugins/zapier-eng-plugin/skills/git-commit
Command: npx skills add https://github.com/zapier/zapier-mcp --skill git-commit-zapier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates storytelling-focused Conventional Commits messages with Jira context integration, then commits and pushes changes. Use when the user says "commit", "git commit", or asks to commit changes, wants to create a commit, or when work is complete and ready to commit.

Core Features & Use Cases

Conventional Commit Messages: Generate complete, story-driven commits that reference Jira tickets and provide context for future readers.
Jira Context Integration: Fetch ticket details to enrich commit messages with summaries, acceptance criteria, and key context.
Workflow: Guide the user through the commit and push steps, ensuring messages follow Conventional Commits.

Quick Start

Say "commit" or "git commit" to begin creating a Conventional Commit message that includes Jira context, then push the changes.

Frequently Asked Questions about Git Commit

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

FAQPage Schema

How do I create a Git commit with Jira context automatically?▼

Git commits can be automated to include Jira context by fetching ticket details and generating Conventional Commit messages that reference your Jira issues. This Skill generates story-driven commits with ticket summaries and acceptance criteria, then pushes changes to your configured repository using SSH or HTTPS authentication.

What is a Conventional Commit message and why should I use one?▼

Conventional Commits follow a standardized format (type, scope, subject) that makes commit history readable and enables automated changelog generation. This Skill generates these messages automatically with Jira context, so future readers understand the work completed and which tickets were addressed.

Can I automate committing changes from Zapier workflows?▼

Yes. This Skill commits updated files and staged changes triggered by Zapier workflows, requiring repository access, a list of changed files or diffs, and authentication credentials for your Git remote. It works across CI/CD pipelines to automate commit creation when workflow steps complete.

Do I need SSH or HTTPS to push commits with this Skill?▼

The Skill supports both SSH and HTTPS authentication for pushing commits to your remote repository. You provide the repository path or URL and authentication method; the Skill handles signing or unsigned commits based on your setup.

What information does this Skill need to create a commit?▼

Provide repository access (path or URL), a list of changed files or diffs, an optional commit message or let the Skill generate one from Jira context, and authentication credentials for your Git remote. The Skill then produces a signed or unsigned commit and pushes the changes.