skills.rest
frostbun
frostbunCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-conventions

Enforce Git best practices for SSH cloning, conventional commits, and branch naming.

Updated Aug 20, 2025
Search Tags:#git#version control#developer workflow#commit messages#branching
One-click install
npx skills add https://github.com/frostbun/dotfiles --skill git-conventions-frostbun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/frostbun/dotfiles/tree/main/configs/opencode/skills/git-conventions
Command: npx skills add https://github.com/frostbun/dotfiles --skill git-conventions-frostbun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides clear guidelines for using Git, ensuring consistency in how code is managed and committed across a team.

Core Features & Use Cases

  • SSH Cloning: Promotes secure and standard repository access.
  • Conventional Commits: Enforces a structured format for commit messages, improving readability and enabling automated changelog generation.
  • Branch Naming: Establishes a predictable system for naming branches based on their purpose.
  • Use Case: When starting a new feature, use feature/your-feature-name for your branch and commit your changes using the conventional commit format like feat: implement user login.

Quick Start

Use the git-conventions skill to understand how to name your branches and format your commit messages.

Frequently Asked Questions about git-conventions

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

FAQPage Schema
What are conventional commits and how do they structure git commit messages?▼

Conventional commits structure git commit messages by enforcing defined commit types and scopes, like `feat:` for new features. This structured format improves readability and enables automated changelog generation for consistent code management.

How do I name git branches for feature development and bug fixes?▼

You name git branches by establishing a predictable system based on their purpose, such as using `feature/your-feature-name` for new features. This branch naming convention ensures a standardized developer workflow across your team.

Does this git workflow standardization support secure SSH cloning?▼

Yes, this git workflow standardization supports secure SSH cloning. It promotes secure and standard repository access to ensure consistent code management across all software development workflows involving version control.

What is the best way to standardize developer workflow for version control across a team?▼

The best way to standardize developer workflow for version control is to enforce git best practices for SSH cloning, conventional commit messages, and branch naming conventions. This ensures consistency in how code is managed and committed across a team.

When do I need to use defined commit types and scopes in my commit messages?▼

You need to use defined commit types and scopes in your commit messages whenever you are applying conventional commit formats to your version control workflow. Adherence to these defined patterns is required for consistent code management and automated changelog generation.

Related Skills

Explore More Software Engineering Skills→
sheer-reysheer-rey

chinese-git-workflow

Configure Git workflows for Chinese-hosted repositories on Gitee, Coding.net, Jihu GitLab, CNB, and mirrored GitHub.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
hyperlisthyperlist
271

git-workflow

Enforce Git branching, commit, and pull request standards with automated staging.

Community
Intermediate
gongye19gongye19

git-workflow

Enforce Git workflow best practices for commits, branches, and pull requests.

Community
Intermediate