skills.rest
SwiftyJunnos
SwiftyJunnosCOMMUNITY
Explore all skills by this author →
GitHub

git-committer

Analyze staged Git changes and generate conventional commit messages.

Updated Nov 10, 2025
Search Tags:#git#code review#version control#commit#conventional commits#submodules
One-click install
npx skills add https://github.com/SwiftyJunnos/Claude-Code-with-TDD --skill git-committer-swiftyjunnos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-committer
Source: https://github.com/SwiftyJunnos/Claude-Code-with-TDD/tree/main/.claude/skills/git-committer
Command: npx skills add https://github.com/SwiftyJunnos/Claude-Code-with-TDD --skill git-committer-swiftyjunnos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of creating meaningful Git commits, ensuring adherence to conventional commit standards and preventing common pitfalls like committing sensitive information or mixing unrelated changes.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes staged changes to suggest well-formatted commit messages.
  • Logical Change Grouping: Groups related changes into distinct commits, offering single or multiple commit strategies.
  • Submodule Handling: Prioritizes and correctly commits submodule changes before the parent repository.
  • Use Case: After completing a new feature, use this Skill to automatically generate a feat: commit message, ensuring it includes all related code, tests, and documentation changes, and handles any submodule updates correctly.

Quick Start

Use the git-committer skill to analyze staged changes and create a commit.

Frequently Asked Questions about git-committer

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

FAQPage Schema
How do I generate conventional commit messages from staged git changes?▼

Conventional commit messages are generated by analyzing staged git changes to group related modifications into logical units, suggesting well-formatted commit options, and executing only after user confirmation. This prevents mixing unrelated changes and ensures format adherence.

What is the best way to handle git submodules during the commit process?▼

Git submodule commits should be prioritized and executed before the parent repository commit. This ensures submodule updates are correctly tracked within the parent repository's commit history, preventing reference mismatches.

How do I split mixed staged changes into multiple logical commits?▼

Mixed staged changes are split by analyzing the diff to group related modifications into distinct logical units. The process then presents multiple commit strategies, allowing you to select between a single consolidated commit or multiple separated commits.

Can I review and edit automated git commit messages before execution?▼

Yes, you can review automated git commit messages before execution. The workflow always waits for explicit user confirmation before applying any commit to the repository, ensuring you retain full control over the final commit history.

Does this commit generation approach work without external version control dependencies?▼

Yes, this approach works without external dependencies. It operates directly on your staged git changes and submodule references using internal scripts and references, requiring no additional version control packages or external integrations.

Related Skills

Explore More Software Engineering Skills→
delorenjdelorenj

openclaw-runtime-git

Manage the openclaw-runtime Git repository and agent workspace submodules.

Community
Intermediate
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
Cogni-AI-OUCogni-AI-OU

pre-commit

Automate pre-commit checks for formatting, linting, and security on staged files.

Official
Advanced
JannaelJannael
16

caveman-commit

Generates Git commit messages adhering to Conventional Commits format with strict subject and body rules.

Community
Intermediate