commit

Generate conventional git commit messages with type prefixes and co-authored-by trailers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated creation of well-formed git commits from the current working tree and session history to ensure clarity and traceability.

Core Features & Use Cases

  • Generate conventional commits with type prefixes (feat, fix, etc.) that reflect changes and intent.
  • Include both a concise subject and a detailed body with rationale, followed by a Co-authored-by trailer when applicable.
  • Validate staging and diffs to ensure only intended changes are committed and wrap lines to 72 characters.

Quick Start

Ask Claude Code to generate a commit message from your session history and current git changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from git changes?

You can generate conventional commit messages by analyzing current git diffs and session history to produce type-prefixed subjects, detailed bodies with rationale, and co-authored-by trailers that satisfy standard formatting requirements.

What is the best way to include session history context in a git commit?

Including session history in a git commit involves extracting development context to build a detailed message body that explains the rationale behind code changes, ensuring traceability between the conversation logic and the final version control output.

Can I validate staged diffs before writing a commit message?

Yes, validating staging and diffs before committing ensures only intended changes are included in the final git commit, preventing unintended files from being added to the version control history.

How do I format git commit subjects and bodies to meet line length limits?

Formatting git commits to meet line limits involves wrapping commit subjects and body content to 72 characters while maintaining a concise summary and a detailed explanation of the code changes.

Does automated commit generation work without external dependencies?

Yes, automated commit generation can function entirely without external dependencies, relying only on the existing git working tree and session history to construct well-formed conventional commit messages.

When do I need a co-authored-by trailer in conventional commits?

A co-authored-by trailer is needed in conventional commits when an automated tool assists in generating the commit message, ensuring proper attribution is appended to the final version control history.