commit

Generate conventional-format git commit messages with rationale from session history.

16|2|Updated Mar 29, 2018
One-click install
npx skills add https://github.com/khoi/dotfiles --skill commit-khoi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/khoi/dotfiles/tree/main/chezmoi/dot_agents/skills/commit
Command: npx skills add https://github.com/khoi/dotfiles --skill commit-khoi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you craft well-formed git commits from the current work changes by leveraging session history for rationale and a succinct summary.

Core Features & Use Cases

  • Generate atomic, rationale-backed commit messages that follow conventional-commit style.
  • Analyze git status and diffs to produce a coherent subject line and body that describe changes and intent.
  • Validate staging decisions by ensuring only relevant hunks are included and guiding the final commit composition.

Quick Start

Issue a commit message proposal based on your session history and staged changes, and apply it to your working tree.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commits from git diffs and session history?

You can generate conventional commits by analyzing staged git diffs alongside your session history to extract rationale. This produces a coherent subject line and detailed body, validating that only relevant codebase hunks are included.

What is the best way to write a detailed commit message with rationale for code reviews?

Writing a detailed commit message with rationale is best handled by leveraging session history to summarize your intent. This approach ensures the commit body clearly describes changes and the reasoning behind them for effective code reviews.

Can I automate git commit message creation for staged changes?

Yes, you can automate git commit message creation by applying this skill to your working tree. It analyzes your staged changes and session history to propose a well-formed, conventional-commit message automatically.

Does this commit generation approach validate staging decisions before committing?

Yes, this commit generation approach validates staging decisions by ensuring only relevant hunks are included. It analyzes the git status and diffs to guide the final commit composition and prevent irrelevant code from being committed.

How do I ensure my git commits follow the conventional-commits format?

To ensure your git commits follow the conventional-commits format, the skill applies parsing rules to your session history and diffs. It generates an atomic commit with a standardized subject and body that adhere to the required format.