commit

Analyze git status and diffs to generate conventional commit messages.

114|29|Updated Nov 23, 2019

Search Tags:#automation #git #workflow #commit #coding #message #conventional-commit

Ready to run

npx skills add https://github.com/helderberto/dotfiles --skill commit-helderberto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/helderberto/dotfiles/tree/main/claude/.claude/skills/commit
Command: npx skills add https://github.com/helderberto/dotfiles --skill commit-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid inconsistent commit messages by analyzing the repository status, diffs, and history to propose concise, pattern-aligned commits.

Core Features & Use Cases

Review git status and diffs to determine what changed and should be included in the commit.
Infer an appropriate commit message style based on project conventions (e.g., conventional commits) and the existing history.
Stage files explicitly and commit using a controlled HEREDOC workflow to ensure messages match the repo's conventions.

Quick Start

Run the commit skill to generate and apply a properly formatted commit message for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate git commit messages to follow conventional commit standards?▼

To automate git commit messages, this Skill analyzes your git status, diffs, and history to infer the change scope and type, then formats the message using a controlled HEREDOC workflow with explicit file staging.

What is the best way to generate consistent commit messages for bug fixes and features?▼

The best way to generate consistent commit messages is to analyze repository history and diffs to propose pattern-aligned messages, ensuring that feature work and bug fixes match your project's existing conventions.

How do I stage files and commit with a formatted message automatically?▼

You stage files and commit automatically by running the Skill, which explicitly stages the modified files and applies a properly formatted commit message via a controlled HEREDOC workflow.

Can I use this to infer commit message style from existing project conventions?▼

Yes, you can use this to infer commit message style because it reviews your existing git history and diffs to propose concise, pattern-aligned messages that satisfy your repository's specific formatting conventions.

Does this workflow support standard git commands for reviewing diffs and history?▼

Yes, the workflow supports standard git commands by reviewing git status and diffs to determine what changed, analyzing the history to infer the style, and staging files explicitly before committing.

Why should I standardize my git workflow with controlled commit formatting?▼

You should standardize your git workflow to avoid inconsistent commit messages, which makes it easier to track feature work, bug fixes, and documentation updates across software development repositories.