commit

Creates git commits with concise Conventional Commits-style subject lines.

Updated Feb 22, 2024
One-click install
npx skills add https://github.com/tlipoca9/dotfiles --skill commit-tlipoca9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/commit
Command: npx skills add https://github.com/tlipoca9/dotfiles --skill commit-tlipoca9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted git commit messages is repetitive and often inconsistent across a project. This Skill standardizes commit creation by enforcing a Conventional Commits-style format and handling staging decisions safely. ## Core Features & Use Cases - Conventional Commits Format: Generates subjects in the form <type>(<scope>): <summary> with types like feat, fix, docs, refactor, chore, test, and perf. - Selective Staging: Honors user-provided file paths or globs to limit which changes get committed, and asks for clarification when files are ambiguous. - Scope Discovery: Optionally reviews recent commit history (git log) to reuse commonly used scopes for consistency. - Use Case: After editing several source files, ask the assistant to commit only the parser changes; it reviews git status and git diff, stages just those files, and commits with a message like fix(parser): handle empty input tokens. ## Quick Start Ask the assistant to commit the current changes, optionally naming specific files or extra instructions for the message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a Conventional Commits message?▼

Use the format `<type>(<scope>): <summary>`, where type is required (feat, fix, docs, refactor, chore, test, perf), scope is an optional short noun, and summary is an imperative phrase under 72 characters with no trailing period.

How to commit only specific files in git?▼

Provide file paths or globs along with your commit request, and only those files will be staged and committed. If the specified files are ambiguous or extra changes exist, you will be asked which files to include before committing.

Does this commit workflow push changes to the remote?▼

No, it only creates local commits and never pushes. It also omits breaking-change footers and sign-off trailers like Signed-off-by, keeping the commit limited to a subject and optional body.

What commit types should I use for bug fixes and features?▼

Use `feat` for new features and `fix` for bug fixes. Other common types include docs, refactor, chore, test, and perf, chosen based on the nature of the change being committed.

When should a git commit include a body?▼

The body is optional and only needed when the subject cannot fully explain the change. Add a blank line after the subject and write short paragraphs describing the motivation or important details.