commit-message

Generate semantic git commit messages with tiered deterministic and LLM fallback logic.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bizcad/RoadTrip --skill commit-message-bizcad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/bizcad/RoadTrip/tree/main/skills/commit-message
Command: npx skills add https://github.com/bizcad/RoadTrip --skill commit-message-bizcad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates generation of semantic commit messages using a cost-optimized Tier 1→2→3 approach, balancing quality and API costs.

Core Features & Use Cases

  • Tier 1: deterministic commit messages for simple changes (e.g., single file edits in src/)
  • Tier 2: LLM fallback for complex diffs and multi-file changes
  • Tier 3: user override to bypass tiers when needed
  • Supports Conventional Commits formatting and integrated cost tracking for auditing

Quick Start

Stage your changes and optionally provide a -Message override to receive a conventional commit message.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I generate Conventional Commits messages automatically?

You generate Conventional Commits messages by staging git changes and letting the Skill apply deterministic rules for simple diffs or an LLM fallback for complex changes to output the formatted commit text.

What is the best way to reduce LLM API costs when writing commit messages?

To reduce LLM API costs for commit messages, use a tiered approach that applies 0-cost deterministic rules for simple edits and only invokes an LLM fallback for complex multi-file diffs.

Does this commit message generator work with simple staged changes?

Yes, it works with simple staged changes by evaluating single-file edits deterministically in a Tier 1 path, generating standard commit messages without invoking an LLM or incurring API costs.

Can I override the automatic commit message generation?

Yes, you can override the automatic generation by providing an explicit message input, which bypasses the Tier 1 deterministic and Tier 2 LLM evaluation paths to use your custom text directly.

How does cost tracking work for LLM-generated commit messages?

Cost tracking works by integrating with a configuration-driven tier policy that logs API expenditures when the Tier 2 LLM service is invoked, providing an auditable record of generation costs.

When should I not use deterministic rules for commit messages?

You should not use deterministic rules for complex diffs or multi-file changes, as these scenarios require the Tier 2 LLM fallback to accurately summarize semantic changes into Conventional Commits format.