commit-message

Create file-based Git commit messages and apply them with git -F.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing commit messages manually leads to inconsistent formats and reduced traceability. This Skill enforces file-based messages that are created in a temp file and applied with git -F, ensuring uniform style and better history readability.

Core Features & Use Cases

  • Generates a structured commit message from a brief summary and optional body, stored in a temporary file.
  • Applies the message using git commit -F to enforce content from the file, avoiding -m.
  • Provides a quick workflow to review diffs, draft a message, commit, and clean up.

Quick Start

Create a commit message in a temporary file and commit using that file with git -F.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I standardize Git commit messages for better traceability?

Standardize Git commit messages by writing structured content into a temporary file and applying it with git commit -F, which enforces consistent formatting and improves history readability.

Why should I use a file-based Git commit workflow instead of git -m?

A file-based Git commit workflow avoids git -m by using git commit -F to apply a structured message from a temp file, reducing inconsistent formatting and ensuring better traceability.

What's the best way to review staged changes before writing a commit message?

Review staged changes before writing a commit message by displaying diff context, drafting a summary and optional body into a temporary file, then committing and cleaning up.

Can I use this file-based commit workflow for unstaged Git changes?

Yes, the file-based commit workflow supports local development involving both staged and unstaged Git changes, generating a structured message and applying it with git commit -F.

How do I generate a structured commit message from staged Git changes?

Generate a structured commit message from a brief summary and optional body, store it in a temporary file, and apply it using git commit -F to ensure uniform style.

Are there limitations to using a temporary file for Git commit messages?

Using a temporary file for Git commit messages requires cleanup after the commit to avoid leftover artifacts, and it avoids git -m entirely to enforce file-based content.