skills.rest
ntluong95
ntluong95COMMUNITY
Explore all skills by this author →
WebsiteGitHub

Git & Collaboration Standards

Enforce Git commit, branch, and pull request standards.

Updated Mar 7, 2026
Search Tags:#git#collaboration#version control#branching#commits#pull requests
One-click install
npx skills add https://github.com/ntluong95/agent-skills-statistics --skill git-collaboration-standards-ntluong95
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git & Collaboration Standards
Source: https://github.com/ntluong95/agent-skills-statistics/tree/main/.github/skills/common/git-collaboration
Command: npx skills add https://github.com/ntluong95/agent-skills-statistics --skill git-collaboration-standards-ntluong95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes clear, consistent guidelines for version control and team collaboration, preventing common issues like messy commit histories and merge conflicts.

Core Features & Use Cases

  • Conventional Commits: Enforces a standardized format for commit messages for better readability and automation.
  • Branching Strategy: Guides the creation and management of feature branches to maintain a clean and stable main codebase.
  • Pull Request Standards: Outlines best practices for creating effective pull requests, ensuring thorough reviews and smooth integration.
  • Use Case: When starting a new feature, you'll create a branch named feat/user-authentication and ensure all your commits follow the feat(auth): add login endpoint format before opening a pull request.

Quick Start

Use the git collaboration skill to ensure your next commit message follows the conventional commits standard.

Frequently Asked Questions about Git & Collaboration Standards

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

FAQPage Schema
How do I enforce conventional commits format for git version control?▼

To enforce conventional commits for git version control, apply standardized message formatting using prefixes like feat or fix, ensuring better readability and automation for your team's commit history.

What is the best way to manage feature branches to maintain a stable main codebase?▼

Managing feature branches to maintain a stable main codebase requires creating descriptive branches like feat/user-authentication and applying a strict branching strategy before integrating changes into the main branch.

How do I maintain a linear git history when collaborating with a team?▼

Maintaining a linear git history when collaborating with a team requires rebasing commits instead of merging, ensuring a clean and straight project timeline without unnecessary merge commits.

What should be included in pull request standards for thorough code reviews?▼

Pull request standards for thorough code reviews should outline best practices for creating effective pull requests, ensuring proper integration and adherence to atomic commits and conventional formatting.

When do I need atomic commits in my branching strategy?▼

You need atomic commits in your branching strategy when you want each commit to represent a single, self-contained logical change, preventing messy commit histories and reducing potential merge conflicts.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
sebnowsebnow
8

source-control-hygiene

Enforce atomic commits with conventional messages across git and jujutsu workflows.

Community
Advanced
barikata1984barikata1984

quality-review

Automates git-based code quality reviews for commits and pull requests.

Community
Intermediate
markus41markus41
1

gitworfkflows

Manage Git branching, commits, rebasing, and pull requests.

Community
Basic