commit

Automate git commits with submodule checks and staged change review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a git commit following project commit message conventions, with full support for repositories using git submodules. Handles submodule changes before parent repository commits.

Core Features & Use Cases

  • Submodule-change aware commits that first resolve submodule changes
  • Deterministic multi-step workflow: inspect submodules, review staged changes, draft messages, and commit
  • Works for repositories with or without submodules, and for standard commits or saving work

Quick Start

Run a submodule-aware commit workflow for the current repository.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit changes in a git repository with submodules?

To commit changes in a git repository with submodules, you must first resolve and commit the changes within the submodules themselves before committing the parent repository. A deterministic workflow inspects submodule changes, reviews staged files, drafts a message, and commits.

What is the correct workflow for git commits with submodules?

The correct workflow for git commits with submodules involves a deterministic sequence: checking submodules for changes, reviewing staged changes, drafting a structured commit message, confirming the details, and executing the commit for both submodule and parent repositories.

Can I use a standard commit workflow for repositories without submodules?

Yes, you can use the same workflow for repositories without submodules. The process works for both simple and submodule-rich repositories, skipping the submodule checks and proceeding directly to reviewing staged changes and drafting a structured commit message.

How do I draft a structured git commit message following project conventions?

To draft a structured git commit message following project conventions, you review your staged changes and generate a message that adheres to the established formatting rules. The workflow guides you through staging review and message drafting before final confirmation.

Why does my parent repository commit fail when submodules have changes?

Your parent repository commit fails or leaves dirty states because submodule changes must be handled before parent repository commits. You need a submodule-aware workflow that first commits the submodule changes, then stages and commits the updated submodule reference in the parent repository.