commit

Identify working tree changes and craft conventional-commit messages with session history.

Updated Mar 22, 2026

Search Tags:#git #commit #code-review #version-control #conventional-commits #session-history #message-generation

Ready to run

npx skills add https://github.com/airhorns/jam --skill commit-airhorns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/airhorns/jam/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/airhorns/jam --skill commit-airhorns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating meaningful, standards-compliant git commits from a messy working tree can be error-prone and time-consuming. This skill uses session history and actual changes to generate concise, well-structured commit messages with rationale and a proper body.

Core Features & Use Cases

Rationale-aware messages: generate commit subject and body that include reasoning from session history.
Conventional-commit compliant: format with type/scope, subject, body, and Co-authored-by trailer.
Staging validation: sanity-check changes and warn about noisy artifacts.
Use Case: When preparing commits after multiple steps or across sessions, ensuring clear history.

Quick Start

Identify changes in your working tree and use session history to compose a well-formed commit message.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate a conventional commit message from session history?▼

Conventional commits use a type/scope prefix, a concise subject, a body explaining the rationale, and optional Co-authored-by trailers. This skill automatically enforces these structural rules and subject length limits when composing your message.

Can I use session history to craft a git commit message with a proper body?▼

Yes, you can use session history to craft a git commit message with a proper body. The skill analyzes your development session to extract reasoning and applies it to generate the commit body rationale alongside the subject.

What is the best way to prepare staged work for a git commit?▼

The best way to prepare staged work for a git commit is to sanity-check the changes for noisy artifacts first. This skill validates your staging area and warns about problematic files before finalizing the commit message.

Does this git commit skill validate changes before finalizing the commit?▼

Yes, this git commit skill validates changes before finalizing the commit. It performs staging validation to sanity-check your working tree and proactively warns you about noisy artifacts that should not be committed.

Why does my conventional commit message need a body and rationale?▼

A conventional commit message needs a body and rationale to explain the reasoning behind the code changes. This skill uses session history to capture the context of multiple development steps, ensuring you maintain a clear and understandable version-control history.