commit

Enforce git commit messages without AI attribution or Co-Authored-By headers.

22|5|Updated Jan 9, 2018
One-click install
npx skills add https://github.com/tdhopper/dotfiles2.0 --skill commit-tdhopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/tdhopper/dotfiles2.0/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/tdhopper/dotfiles2.0 --skill commit-tdhopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure commits are created without AI attribution and without Co-Authored-By headers, preserving project contribution integrity and reviewer clarity.

Core Features & Use Cases

  • Enforce attribution policies during commit creation.
  • Validate commit messages against rules and provide guidance to maintainers.
  • Use in team workflows to prevent accidental leakage of attribution or headers in commits.

Quick Start

Craft a compliant git commit message that avoids AI attribution and Co-Authored-By headers.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I remove Co-Authored-By headers from my git commits?

To remove Co-Authored-By headers from git commits, enforce attribution policies during commit creation to eliminate unintended headers. This validates messages against rules to preserve contribution integrity and reviewer clarity.

How do I prevent AI attribution in version control commit messages?

Preventing AI attribution in version control commit messages requires enforcing compliant commit creation rules that strip automated tags. This maintains project contribution integrity by avoiding accidental leakage of AI attribution headers.

What is git commit compliance and why is it important for collaborative repositories?

Git commit compliance ensures commits are created without AI attribution or Co-Authored-By headers, preserving project contribution integrity. It is important for collaborative repositories to maintain reviewer clarity and prevent accidental attribution leakage.

Can I use automated commit guidance to enforce attribution policies in team workflows?

Yes, you can use automated commit guidance to enforce attribution policies in team workflows. It serves as a checklist within the commit process to validate messages and prevent accidental leakage of attribution or headers in collaborative repositories.

How do I validate git commit messages against attribution rules before finalizing?

Validate git commit messages against attribution rules by applying compliance checks during the commit creation process. This guidance ensures no AI attribution or Co-Authored-By headers are present before the commit is finalized.