git

Generate conventional commit messages and pull request descriptions.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Kang-chen/Agent-skills --skill git-kang-chen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/Kang-chen/Agent-skills/tree/main/git
Command: npx skills add https://github.com/Kang-chen/Agent-skills --skill git-kang-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized approach to writing commit messages and PR descriptions based on conventional commits, reducing ambiguity and improving traceability across the codebase.

Core Features & Use Cases

  • Structured commits: Enforces a consistent type, optional scope, and concise description for every commit.
  • PR guidance: Standardizes PR titles and descriptions to speed up reviews and maintain clarity.
  • Code review clarity: Improves review context by requiring explicit message formats and rationale.

Quick Start

Write a commit message like "feat(auth): add OAuth login flow" and a PR description following the same convention.

Frequently Asked Questions about git

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

FAQPage Schema
What are conventional commits and how do they improve Git workflows?

Conventional commits standardize commit messages using structured types, optional scopes, and clear description rules to reduce ambiguity and improve traceability across a software codebase.

How do I write a conventional commit message for a new feature?

To write a conventional commit message, start with a type like feat, add an optional scope in parentheses, end with a concise description, such as feat(auth): add OAuth login flow.

How do I format pull request titles and descriptions for faster code review?

Format pull request titles and descriptions by applying conventional commit guidelines to provide explicit message formats and rationale. Standardizing PR formats speeds up reviews and maintains clarity.

What commit types should I use for documentation or refactoring changes?

For documentation or refactoring changes, use the docs or refactor commit types. Structuring your messages with these specific prefixes enforces consistent guidelines and improves traceability across your software team.

Can I use conventional commits for both commits and pull requests in my team workflow?

Yes, conventional commits apply to Git workflows across software teams, covering creating commits, drafting messages, and composing PR descriptions. This consistency enforces review guidelines and maintains traceability.