skills.rest
scooter-lacroix
scooter-lacroixCOMMUNITY
Explore all skills by this author →
Website𝕏@scooter_lacroixGitHub

git-commits

Enforce user-authored Git commit messages and capture reasoning in reasoning.md.

8|1|Updated Jan 4, 2026
Search Tags:#git#workflow#version control#commit#code history#ai attribution
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill git-commits-scooter-lacroix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/git-commits
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill git-commits-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents AI-generated attribution lines from being included in Git commits, ensuring that commits appear authored by the user.

Core Features & Use Cases

  • Clean Commits: Automatically removes "Generated with Maestro" and Co-Author lines.
  • Reasoning Capture: Generates a reasoning.md file to document the commit's context.
  • Use Case: When you've finished a coding task and want to save your work, using this skill ensures your Git history remains clean and professional.

Quick Start

When prompted to commit, use the commit skill.

Frequently Asked Questions about git-commits

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

FAQPage Schema
How do I remove AI-generated attribution lines from my git commits?▼

To remove AI-generated attribution lines from git commits, use a workflow that strips Co-Author lines and "Generated with" tags before pushing. This ensures your code history remains user-authored and clean.

Can I prevent Co-Author tags from being added to my version control history?▼

Yes, preventing Co-Author tags in version control history is possible by enforcing commit rules that automatically filter out AI attribution lines during save operations, keeping your commit log professional.

How do I document commit reasoning without cluttering my git log?▼

Document commit reasoning without cluttering the git log by writing the context to a separate reasoning.md file. This captures the commit's background information while maintaining clean commit messages.

What is the best way to keep AI code generation metadata out of my git history?▼

The best way to keep AI code generation metadata out of git history is to enforce commit operations that intercept and delete attribution lines before the changes are saved, ensuring only user-authored messages remain.

Does this git workflow work without additional dependencies or setup?▼

Yes, this git workflow works without additional dependencies, operating through basic scripts to enforce commit rules and capture reasoning, requiring no external setup beyond your existing version control environment.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
thurstonsandthurstonsand

git-commit-helper

Generate conventional commit messages from staged git diffs.

Community
Intermediate
VoDmAlVoDmAl

guard

Block Git commit and push operations until explicit user permission is granted.

Community
Advanced