commit-changes

Group related unstaged and staged changes into conventional commits.

7|Updated Sep 27, 2022
One-click install
npx skills add https://github.com/vieitesss/.mac_config --skill commit-changes-vieitesss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-changes
Source: https://github.com/vieitesss/.mac_config/tree/main/agents/skills/commit-changes
Command: npx skills add https://github.com/vieitesss/.mac_config --skill commit-changes-vieitesss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing code changes requires organizing raw changes into logical commits; this skill helps automate that process and ensure clean history.

Core Features & Use Cases

  • Group related changes from multiple files into separate commits following Conventional Commits.
  • Enforce one-line commit messages, avoid mixing unrelated changes, and skip secrets or sensitive files.
  • Use cases include feature work, bug fixes, and refactors where multiple files are updated together.

Quick Start

Review your working tree and let the tool create grouped, one-line Conventional Commits for each change set.

Frequently Asked Questions about commit-changes

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

FAQPage Schema
How do I group multiple file changes into separate conventional commits?

To group changes into conventional commits, the skill analyzes your unstaged and staged files, identifies related modifications, and splits them into separate cohesive commits with one-line messages.

What is the best way to avoid mixing unrelated changes in a git commit?

To avoid mixing unrelated changes in a git commit, the tool automatically detects logical boundaries between file modifications and enforces separate commits for each distinct change set.

Can I split staged and unstaged changes into cohesive git commits automatically?

Yes, you can split staged and unstaged changes automatically. The skill processes your working tree, groups related modifications, and creates individual conventional commits without manual staging adjustments.

Does this commit grouping tool skip secrets or sensitive files automatically?

Yes, the commit grouping process skips secrets and sensitive files automatically. The tool detects and excludes sensitive data from your working tree before generating conventional commit messages.

Why should I use one-line conventional commit messages for grouped changes?

One-line conventional commit messages keep your git history clean and readable. The tool enforces this format to ensure each grouped change set is concise and follows conventional commit standards.

When do I need to automate splitting changes into separate commits?

You need to automate splitting changes during feature work, bug fixes, or refactors where multiple files are updated together, ensuring logical separation without manual staging and committing.