commit

Analyze Git diffs and create conventional commit messages with staging guardrails.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/gitduk/agents --skill commit-gitduk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gitduk/agents/tree/main/skills/commit
Command: npx skills add https://github.com/gitduk/agents --skill commit-gitduk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of conventional commit messages from changes in a Git repository.

Core Features & Use Cases

  • Analyze both staged and unstaged changes to determine what should be committed.
  • Generate conventional commit messages that follow project conventions and include scope where relevant.
  • Commit the changes with guardrails to avoid accidentally staging secrets or unwanted files; optionally push if requested.

Quick Start

Tell your AI to commit the current changes using a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commits from Git changes?

To generate conventional commits from Git changes, this Skill analyzes staged and unstaged diffs to determine what to stage, then creates formatted commit messages following project conventions and scope.

What is the best way to automate staging and committing code changes safely?

Automating staging and committing code changes safely is best achieved by analyzing diffs to determine what to stage, applying guardrails to prevent staging secrets, and generating conventional commit messages.

How does conventional commit style detection work for version control?

Conventional commit style detection for version control works by analyzing repository diffs and generating commit messages that follow conventional commit formats, including relevant scope based on the changes.

Can I automatically push conventional commits after staging?

Yes, you can automatically push conventional commits after staging. This Skill optionally handles pushing committed changes while applying guardrails to avoid accidentally committing unwanted files.

Does this conventional commit automation protect against staging secrets?

Yes, this conventional commit automation protects against staging secrets. It applies guardrails during the staging and committing process to prevent accidentally staging secrets or unwanted files.

When do I need to analyze unstaged changes before creating a Git commit?

You need to analyze unstaged changes before creating a Git commit when you want to determine exactly what should be committed, ensuring only relevant code changes are staged using the conventional commit format.