skills.rest
EpicenterHQ
EpicenterHQOFFICIAL
Explore all skills by this author →
Website𝕏@EpicenterHQGitHub

git

Prompts users for required infoGit push commits and generates commit messages adhering to formatting and linting conventions.

4.7k|374|Updated Mar 16, 2023
Search Tags:#git#versioning#commits#pull-requests#conventional-commits#pr-guidelines
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill git-epicenterhq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/git
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill git-epicenterhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent commit messages and PR descriptions slow reviews and obscure project history.

Core Features & Use Cases

  • Conventional-commit guidelines: standardize types, scopes, and formats across commits and PR descriptions.
  • Scope usage and examples: encourages precise module names in parentheses after the type.
  • Breaking changes handling: supports explicit BREAKING CHANGE notes in footers.

Quick Start

Create a conventional-commit message for your change, for example: feat(api): add endpoint for user search.

Frequently Asked Questions about git

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

FAQPage Schema
What are conventional commits in Git and why use them?▼

Conventional commits standardize Git commit messages by enforcing specific types, scopes, and description formats. This structured approach clarifies project history and speeds up pull request reviews across software development teams.

How do I format a conventional commit message for a new feature?▼

Format a conventional commit message by specifying the type, an optional scope in parentheses, and a concise description. For example, feat(api): add endpoint for user search indicates a new feature in the api module.

How should breaking changes be documented in conventional commit messages?▼

Document breaking changes in conventional commit messages by adding explicit BREAKING CHANGE notes in the footer section. This ensures reviewers immediately recognize modifications that introduce incompatible API or logic alterations.

Can this conventional commit standard be applied to pull request descriptions too?▼

Yes, the conventional commit standard applies to both Git commit messages and pull request descriptions. It enforces consistent type, scope, description formatting, and footer conventions across commit creation, review, and PR drafting.

Do I need any specific Git extensions to enforce conventional commit guidelines?▼

No specific Git extensions are required. The guidelines focus on standardizing commit message and pull request text formatting, relying on structural rules for types, scopes, breaking changes, and footers rather than external dependencies.

What is the correct way to specify a module scope in a conventional commit?▼

Specify a module scope in a conventional commit by placing the precise module name in parentheses immediately after the type. For example, fix(auth): resolve token expiration scopes the fix to the auth module.

Related Skills

Explore More Software Engineering Skills→
inakaminakam

conventional-commit

Generates Japanese Conventional Commit messages and executes git commits for detected repository changes.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
nashgaonashgao
3

Smart Pull Request Command

Manage GitHub and GitLab pull request creation, review, and merging.

Community
Advanced
JackSmack1971JackSmack1971

git-commit-standards

Configure pre-commit hooks to validate conventional commit messages.

Community
Intermediate