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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating well-formatted, atomic Git commits, ensuring your commit history is clean, organized, and follows conventional standards.

Core Features & Use Cases

  • Automatic Grouping: Intelligently groups related changes into single commits.
  • Conventional Commits: Generates commit messages adhering to the <type>: <description> format.
  • Atomic Commits: Creates separate commits for distinct logical changes, even if they involve the same file.
  • Use Case: After making several unrelated changes to your codebase, use this Skill to automatically create individual commits for dependency updates, new feature implementations, and formatting fixes.

Quick Start

Use the commit skill to stage and commit all your current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
What is a conventional commit message and when should I use it?

Conventional commit messages follow the `<type>: <description>` format to keep version control history clean. This format categorizes changes by type, making logical changes easier to track.

Can I split a single file's changes into separate atomic commits?

Yes, you can split a single file's changes into separate atomic commits. The Skill creates distinct commits for separate logical changes even if they involve the same file, keeping version control organized.

Do I need Git CLI installed to automate conventional commit generation?

Yes, Git CLI is required to automate conventional commit generation. The Skill uses Git CLI for version control operations to stage and commit work across your codebase.

What are the limitations of automating atomic commits with this approach?

The approach requires Git CLI for version control operations and applies to staging and committing work across various file types. It works best when distinct logical changes can be clearly identified.