git-commit-conventions

Name: git-commit-conventions
Availability: InStock
Author: TashanGKD

Normalize and validate Git commits and pull requests against conventional commit standards.

5|3|Updated Feb 19, 2026

Search Tags:#git #commit messages #branch naming #push workflow #commit authoring

Ready to run

npx skills add https://github.com/TashanGKD/Tashan-TopicLab --skill git-commit-conventions-tashangkd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-conventions
Source: https://github.com/TashanGKD/Tashan-TopicLab/tree/main/.codex/skills/git-commit-conventions
Command: npx skills add https://github.com/TashanGKD/Tashan-TopicLab --skill git-commit-conventions-tashangkd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures Git commits are standardized for maintainability and collaboration, solving issues like inconsistent commit messages, incorrect branch names, and broken history.

Core Features & Use Cases

Commit Normalization: Standardize commit messages, branch names, and commit authors.
PR History Cleanup: Normalize the history of pull requests with multiple commits.
Author and Committer Identity Management: Replace the AI's identity with that of a contributor upon request.
Safe Pushes: Guide users in pushing history with minimal impact to others.

Quick Start

Apply the git-commit-conventions skill to ensure proper Git commit standards.

Frequently Asked Questions about git-commit-conventions

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

FAQPage Schema

How do I normalize and validate Git commit messages for consistent history?▼

To normalize Git commit messages, apply conventional commit standards to standardize prefixes, branch names, and push strategies. This ensures your repository maintains a reviewable and consistent history across collaborative development workflows.

What is the best way to clean up pull request history with multiple commits?▼

Cleaning up pull request history involves normalizing multiple commits within a PR according to conventional commit standards. This standardizes commit authors and messages, ensuring the integrated history remains maintainable and consistent.

Can I replace the AI committer identity with a specific contributor's identity?▼

Yes, you can manage author and committer identity by replacing the AI's identity with that of a requested contributor. This ensures commits are accurately attributed to the proper developer while maintaining conventional commit standards.

Does this conventional commit validation work with CI/CD pipelines and open-source projects?▼

Yes, conventional commit validation is explicitly designed for development workflows requiring strict commit practices, including CI/CD pipelines and open-source projects. It enforces proper Git commit hygiene and branch naming standards.

How do I execute safe pushes when normalizing Git history?▼

Executing safe pushes involves guiding users in pushing normalized history with minimal impact to other collaborators. This prevents broken history and ensures strict commit practices are maintained without disrupting the shared repository.