commit

Stage intended files and write conventional, why-focused commit messages.

9|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/ivy/dotfiles --skill commit-ivy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ivy/dotfiles/tree/main/home/dot_claude/skills/commit
Command: npx skills add https://github.com/ivy/dotfiles --skill commit-ivy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure intentional changes and well-structured commit messages, improving traceability and reducing accidental commits.

Core Features & Use Cases

  • Selective staging: prevents using git add -A or git add ., ensuring only intended changes are included.
  • Conventional commits: guides subject lines, scope, and formatting to improve readability in history.
  • Amend workflow: supports --amend to fix messages or staged content without losing context.

Quick Start

Stage only the intended files and craft a conventional commit message following the guidelines.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional commit messages for git repositories?

Conventional commit messages require structured subject lines, specific scopes, and why-focused descriptions. This skill guides formatting and mood emoji guidelines to improve readability and maintain a consistent version control history across multi-file edits.

How can I prevent accidental commits when staging multiple files?

To prevent accidental commits during staging, avoid using git add -A or git add . entirely. This skill enforces selective staging of individual files, ensuring only intended changes are included in your version control workflow.

Does this commit workflow support amending staged content and messages?

Yes, the amend workflow supports using git commit --amend to fix messages or modify staged content. This allows you to correct formatting and update staged files without losing the context of your original changes.

What is the best way to enforce intentional git commits in a multi-file edit workflow?

The best way to enforce intentional git commits is by applying strict constraints on git usage and selective staging. This skill checks staged changes and crafts conventional messages, ensuring precise changes and a maintainable history.

Why should I use selective staging instead of git add . for version control?

Selective staging prevents unintended files from entering your repository history. By enforcing intentional file-by-file additions instead of git add ., this skill reduces accidental commits and improves project traceability across your workflow.