commit

Generate conventional Git commit messages from diffs and recent logs.

2|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/cboone/cboone-cc-plugins --skill commit-cboone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cboone/cboone-cc-plugins/tree/main/plugins/commit/skills/commit
Command: npx skills add https://github.com/cboone/cboone-cc-plugins --skill commit-cboone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Git commits by generating context-aware, well-structured messages and handling various commit workflows automatically.

Core Features & Use Cases

  • Conventional Commits: Automatically generates commit messages adhering to conventional commit standards.
  • Contextual Analysis: Analyzes diffs and recent commit history to inform message generation.
  • Workflow Variants: Supports options like committing only staged changes, pushing after commit, and handling plan files.
  • Use Case: After making several code changes, you can simply say "commit the changes with a push" and the Skill will analyze your diff, create a descriptive conventional commit message, stage all changes (excluding secrets), commit them, and push to the remote.

Quick Start

Use the commit skill to commit all staged changes and push them to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from git diffs?

Automating conventional commit messages involves analyzing git diffs and recent repository logs to ensure contextual consistency. This Skill automatically generates these messages, stages all changes excluding secrets, and handles the commit process for your workflow.

Can I stage all changes and push to the remote in one automated git workflow?

Yes, you can commit all changes and push to the remote in a single workflow. The Skill stages all changes excluding secrets, generates a descriptive conventional commit message based on the diff, commits them, and executes the push automatically.

What is the best way to maintain commit message consistency across a repository?

Maintaining commit message consistency requires analyzing recent repository logs to match existing project conventions. This Skill examines your commit history and current diffs to ensure newly generated messages strictly adhere to your repository's established formatting standards.

Does the commit workflow handle committing only staged changes instead of all files?

Yes, the workflow explicitly supports committing only staged changes. You can specify a staged-only commit, and the Skill will analyze the staged diff to generate a context-aware conventional commit message without including unstaged file modifications.

How does contextual analysis work when automating version control commits?

Contextual analysis for version control commits works by examining both the current code diff and recent repository logs. This ensures the generated conventional commit message is accurately descriptive and aligns with the existing formatting conventions of the repository.