git-commit

Stages changes and creates small, focused Git commits with informative messages.

24|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/goncalossilva/.agents --skill git-commit-goncalossilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/goncalossilva/.agents/tree/main/skills/git-commit
Command: npx skills add https://github.com/goncalossilva/.agents --skill git-commit-goncalossilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create high-quality Git commits that are small, focused, and have clear, informative messages, leading to a cleaner and more maintainable project history.

Core Features & Use Cases

  • Atomic Commits: Ensures each commit addresses a single logical change.
  • Clear Rationale: Guides the generation of commit messages that explain the 'what' and 'why' of a change.
  • Best Practice Adherence: Enforces common Git commit message conventions and repository-specific styles.
  • Use Case: When you've made several unrelated changes, this skill helps you break them down into individual, well-documented commits before pushing.

Quick Start

Use the git-commit skill to stage all changes and create a new commit with a descriptive message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write good Git commit messages for code review?

Good Git commit messages are imperative and informative, explaining the 'what' and 'why' of a change. The skill guides you to generate clear commit messages adhering to best practices and repository-specific styles for better reviewability.

How do I split multiple unrelated changes into focused Git commits?

To create focused Git commits, you break down unrelated changes into individual, well-documented commits. This skill automates staging changes logically to ensure each commit addresses a single logical change.

What are atomic commits and when do I need them in my development workflow?

Atomic commits ensure each Git commit addresses a single logical change, leading to a cleaner project history. You need them when you have made several unrelated changes and want to break them down before pushing.

Does this Git commit automation work with my repository's specific style?

Yes, this skill enforces common Git commit message conventions while adapting to your repository-specific styles. It ensures commits are small, focused, and avoid sensitive information automatically.

Can I prevent sensitive information from being added to version control?

Yes, you can prevent sensitive information in version control by using this skill. It ensures commits avoid sensitive information while automating the staging and commit process for your development workflow.

What is the best way to automate staging changes and creating a Git commit?

The best way to automate creating a Git commit is using this skill to stage all changes and generate a descriptive message. It ensures commits are small, focused, and follow best practices before execution.