git-commit

Stage code changes and create Conventional Commits with pre-commit checks.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/riddopic/cc-tools --skill git-commit-riddopic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/riddopic/cc-tools/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/riddopic/cc-tools --skill git-commit-riddopic

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of staging changes and creating well-formatted Git commits, ensuring a clean and consistent project history.

Core Features & Use Cases

  • Atomic Commits: Groups related changes into single, logical commits.
  • Conventional Commits: Enforces a standardized format for commit messages (type: description).
  • Pre-commit Checks: Integrates with task pre-commit to ensure code quality before committing.
  • Use Case: After implementing a new feature, use this Skill to inspect all changes, group them into an atomic commit, write a descriptive conventional commit message, and stage only the relevant files.

Quick Start

Use the git-commit skill to stage all changes and create a feat commit with the message "add user authentication".

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate staging changes and creating conventional commits?▼

To automate staging changes and creating conventional commits, you use this skill to group related modifications into atomic commits and enforce a standardized message format. It ensures a clean project history.

What is an atomic commit and when do I need it in version control?▼

An atomic commit groups related code changes into a single, logical commit. You need it in version control to maintain a clean history and ensure each commit represents one cohesive, self-contained modification.

How do I run pre-commit checks before staging code in Git?▼

You can run pre-commit checks before staging code by integrating with task pre-commit commands. This ensures code quality checks are executed automatically during the commit workflow before changes are finalized.

Does this commit workflow enforce a specific commit message format?▼

Yes, this commit workflow enforces the Conventional Commits specification. It requires a standardized type and description format for your commit messages to maintain consistency across your development history.

Can I selectively stage files for an atomic commit instead of staging all changes?▼

Yes, you can selectively stage files for an atomic commit. The process involves inspecting all changes, grouping them logically, and staging only the relevant files to ensure the commit remains focused.