skills.rest
hiiamsky
hiiamskyCOMMUNITY
Explore all skills by this author →
GitHub

git-conventions

Validate Git commit messages, branch names, and PR descriptions against preset conventions.

Updated Apr 4, 2026
Search Tags:#git#workflow#collaboration#commit#guidelines#branch#pr
One-click install
npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill git-conventions-hiiamsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/hiiamsky/multi-agent-dev-team/tree/main/.github/skills/git-conventions
Command: npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill git-conventions-hiiamsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

All agents currently operate with inconsistent Git practices, leading to confusing history, diverging branch strategies, and misaligned PR descriptions.

Core Features & Use Cases

  • Centralized Git conventions that govern commit messages, branch naming, and PR descriptions.
  • Automatically loaded before any git operation to ensure compliance.
  • Improves collaboration and traceability across agents.

Quick Start

Write a commit message using the prescribed TYPE: SUBJECT format and include the issue footer.

Frequently Asked Questions about git-conventions

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

FAQPage Schema
How do I enforce a unified git workflow across multiple agents?▼

You can enforce a unified git workflow by applying centralized conventions that automatically validate commit message types, branch names, and PR descriptions before any git operation executes, preventing inconsistent practices.

What is the standard format for git commit messages in collaborative workflows?▼

A standard git commit message format requires a prescribed TYPE: SUBJECT structure, such as Feat, Modify, or Fix, and mandates including a footer with issue numbers to ensure traceability across collaborative agents.

How do I standardize branch naming conventions for better collaboration?▼

You can standardize branch naming conventions by applying formal rules that govern branch creations across all agents, ensuring every branch adheres to a unified strategy and preventing diverging branch names.

Can I include ADR references in my pull request descriptions?▼

Yes, you can include ADR references in your pull request descriptions. The git conventions support ADR references when needed, alongside mandatory footers containing issue numbers for formal documentation.

Why do my agents have inconsistent git commit histories and misaligned PR descriptions?▼

Agents have inconsistent git commit histories and misaligned PR descriptions when they operate without centralized Git conventions, leading to confusing history and diverging branch strategies during collaboration.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

Git Branches

List and visualize Git branch status with remote tracking and synchronization.

Community
Intermediate
cogine-aicogine-ai
3

new-branch-and-pr

Create a feature branch, commit changes, and open a pull request.

Official
Intermediate
pegasus-isipegasus-isi

commit

Generate Conventional Commits from git status, diffs, and branch metadata.

Official
Intermediate
eysenfalkeysenfalk

git-workflow

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

Community
Advanced