commit

Analyze uncommitted Git changes and generate atomic commits with project guidelines.

349|98|Updated Feb 1, 2018
One-click install
npx skills add https://github.com/shopsys/shopsys --skill commit-shopsys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/shopsys/shopsys/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/shopsys/shopsys --skill commit-shopsys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating well-formatted, atomic, and meaningful Git commits, ensuring code history is clean, understandable, and adheres to project guidelines.

Core Features & Use Cases

  • Analyzes Changes: Reviews staged and unstaged changes to identify logical groupings.
  • Enforces Guidelines: Applies project-specific commit message rules (tense, prefixes, formatting).
  • Atomic Commits: Helps break down complex changes into smaller, manageable commits.
  • Use Case: After making several related changes to a feature, use this Skill to help you structure them into individual, well-described commits that clearly explain the 'what' and 'why' of each change.

Quick Start

Use the commit skill to analyze my current changes and propose commit groups.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create atomic git commits from multiple unrelated changes?

To create atomic git commits, you group changes by functionality, type, and scope. This skill analyzes uncommitted changes and proposes logical groupings, ensuring each commit represents a single, manageable update with a properly formatted message.

How do I enforce commit message guidelines like tense and prefixes in git?

Enforcing commit message guidelines requires applying project-specific rules for tense, prefixes, and formatting. This skill automates enforcement by analyzing changes and generating commit messages that strictly adhere to your defined project conventions.

What is the best way to structure complex code changes into smaller git commits?

The best way to structure complex changes into smaller git commits is to identify logical groupings within your code history. This skill reviews staged and unstaged changes, breaking them into individual, well-described commits that explain the what and why.

Can I automate staging and committing files based on their functionality?

Yes, you can automate staging and committing files based on functionality. This skill guides you through staging, groups related modifications, and helps you commit them atomically while handling potential commit failures.

Why should I break down large feature updates into atomic commits?

Breaking down large feature updates into atomic commits keeps your version control history clean and understandable. It ensures each commit represents a specific functional change, making it easier to track project evolution and revert specific updates.