commit-messages

Generate git commit messages and pull request descriptions without AI attribution.

Updated Mar 25, 2020
One-click install
npx skills add https://github.com/daominah/gostructure --skill commit-messages-daominah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/daominah/gostructure/tree/main/.claude/skills/commit-messages
Command: npx skills add https://github.com/daominah/gostructure --skill commit-messages-daominah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unintentional AI attribution and unnecessary metadata from appearing in git commit messages and pull request descriptions, keeping version history focused on business logic.

Core Features & Use Cases

  • No AI Attribution: Instructs authors to avoid co-author trailers, message footers, or any lines that credit AI tools in commits and PRs.
  • Concise Messaging: Encourages short, business-focused summaries that clearly communicate the purpose of changes without verbose bullet lists.
  • Practical Tip: If automated IDE features add attribution, recommend disabling "Commit Attribution" and "PR Attribution" in IDE settings when available.

Quick Start

Write a concise, business-focused commit message and do not include co-author trailers, AI attribution lines, or message footers.

Frequently Asked Questions about commit-messages

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

FAQPage Schema
How do I remove AI attribution from git commit messages?

To remove AI attribution from git commit messages, omit co-author trailers, message footers, and any lines crediting AI tools. Keep commits concise and business-focused, and disable automated Commit Attribution or PR Attribution settings in your IDE if they add these lines automatically.

Why do my pull request descriptions include AI co-author trailers?

Pull request descriptions include AI co-author trailers because automated IDE features generate them. To prevent this, instruct authors to avoid message footers and credit lines, and recommend disabling the PR Attribution settings in your IDE.

What is the best way to write concise git commit messages for pull requests?

The best way to write concise git commit messages is to create short, business-focused summaries that clearly communicate the purpose of changes. Omit verbose bullet lists, co-author trailers, and IDE-generated attribution lines to keep version history focused on business logic.

How do I stop my IDE from adding AI attribution lines to commits?

To stop your IDE from adding AI attribution lines to commits, disable the Commit Attribution and PR Attribution settings in your IDE. This prevents automated co-author trailers and message footers from appearing in your git history.

Should I include AI tool credits in my pull request descriptions?

No, you should not include AI tool credits in your pull request descriptions. Omit co-author trailers and AI attribution lines to ensure your commits remain concise and focused entirely on the business logic of the changes.

Can I use this approach to clean up an existing git history with AI metadata?

This approach applies to developers composing or generating new commit and PR messages. It enforces concise, business-focused summaries by omitting AI attribution, but does not clean up existing git history retroactively.