commit-message

name	commit-message
description	When you need to describe what code changes do - whether for a commit message or PR description. Reads the actual git diff to generate proper conventional commit format with type, scope, and summary. Use when writing commit messages, creating PR descriptions, or summarizing changes.

Instructions

• Use for PR's or commit message's
• this is a git conventional commit format
  • review git-conventional-commits.yaml values in convention.commitTypes for <type>'s available
• the git subject line becomes the PR title
• You MUST follow the exact template

Rules

• Output plain text only. No markdown fences.
• First line MUST be a valid Conventional Commit subject.
• Keep the FIRST line <= 72 characters.
• Use a specific scope when possible.
• Body:
  • a short summary of the PR
  • a few bullet points explaining the main changes
  • Each bullet must describe one complete logical change, including purpose or impact
  • Do not split a single idea across multiple bullets
  • Explain WHAT and WHY
  • Wrap lines to <= 72 chars

Template

():

AI Attribution

Add a Co-authored-by trailer at the end of the commit message body (after the description, before any footer markers like BREAKING CHANGE:):

Co-authored-by: <AI_NAME> <AI_NOREPLY_EMAIL>

Use your AI identity:

AI Name	AI_NAME	AI_NOREPLY_EMAIL
Kimi	Kimi	[e-mail]
Copilot	GitHub Copilot	[e-mail]
Claude	Claude	[e-mail]

---

SPDX-FileCopyrightText: Copyright © 2026 Caleb Cushing

SPDX-License-Identifier: CC-BY-NC-SA-4.0