skills.rest
mihai-chiorean
mihai-chioreanCOMMUNITY
Explore all skills by this author →
𝕏@mihaichioreanGitHub

commit-pr-etiquette

Remove automated AI-generated footers from commit messages and pull request descriptions.

Updated Mar 20, 2026
Search Tags:#git#code review#documentation#pull request#commit#etiquette
One-click install
npx skills add https://github.com/mihai-chiorean/inc --skill commit-pr-etiquette
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-pr-etiquette
Source: https://github.com/mihai-chiorean/inc/tree/main/skills/commit-pr-etiquette
Command: npx skills add https://github.com/mihai-chiorean/inc --skill commit-pr-etiquette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the cluttering of project history by ensuring that automated AI-generated footers and metadata are excluded from commit messages and pull request descriptions.

Core Features & Use Cases

  • Commit Hygiene: Automatically identifies and flags unnecessary Claude Code footers in commit messages.
  • PR Standardization: Ensures pull request descriptions remain clean and focused on human-readable content.
  • Use Case: Use this skill during your code review process to ensure that all contributors adhere to a clean commit message policy, removing any automated signatures before merging.

Quick Start

Ask the agent to review the current commit messages and PR descriptions for any prohibited automated footers.

Frequently Asked Questions about commit-pr-etiquette

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

FAQPage Schema
How do I remove AI generated footers from git commit messages?▼

You can remove AI generated footers from git commit messages by enforcing professional commit standards that automatically identify and flag unnecessary automated metadata before merging.

How do I keep pull request descriptions clean from automated metadata?▼

To keep pull request descriptions clean from automated metadata, you enforce PR standardization practices that ensure documentation remains focused on human-readable content only.

What is commit hygiene for maintaining repository history integrity?▼

Commit hygiene for maintaining repository history integrity is the practice of excluding automated AI-generated footers and metadata from commit messages to prevent cluttering project history.

Can I use this during my code review process to enforce clean commit message policy?▼

Yes, you can use this during your code review process to ensure all contributors adhere to a clean commit message policy, removing any automated signatures before merging.

How do I review current commit messages for prohibited automated footers?▼

You review current commit messages for prohibited automated footers by asking the agent to scan the commit history and PR descriptions to flag unnecessary AI-generated signatures.

Why does automated metadata clutter project history in git workflows?▼

Automated metadata clutters project history in git workflows because it introduces unnecessary AI-generated footers into commit messages and pull request descriptions, degrading repository history integrity.

Related Skills

Explore More Software Engineering Skills→
Binh230199Binh230199
1

git-commit-message

Generate git commit messages from staged, unstaged, or historical changes.

Community
Advanced
raas-devraas-dev
19

finishing-a-development-branch

Verify tests and present merge, PR, keep, or discard options for Git branches.

Official
Intermediate
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
Smooth-OperationSmooth-Operation

pre-commit-hooks

Automate pre-commit checks for linting, formatting, tests, and secrets.

Official
Intermediate