skills.rest
cardoso-neto
cardoso-netoCOMMUNITY
Explore all skills by this author →
GitHub

git-version-control

Enforce Git commit workflow rules for staging, messages, and rebase updates.

3|1|Updated Dec 4, 2025
Search Tags:#git#branching#staging#best-practices#version-control#commit-messages#pull-rebase
One-click install
npx skills add https://github.com/cardoso-neto/personal-ai-infra --skill git-version-control-cardoso-neto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-version-control
Source: https://github.com/cardoso-neto/personal-ai-infra/tree/main/skills/git-version-control
Command: npx skills add https://github.com/cardoso-neto/personal-ai-infra --skill git-version-control-cardoso-neto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

People frequently misuse Git operations, leading to messy histories, accidental large-scale changes, and confusing commits. This skill provides clear guidelines to ensure disciplined commit practices.

Core Features & Use Cases

  • Never use git add -A or git add .; explicitly stage files with git add <filename>.
  • Commit message titles should be imperative, start capitalized, limited to 50 chars, and finish with no punctuation.
  • Do not create branches or commits unless explicitly instructed.
  • When updating from the remote, always use git pull --rebase to avoid unnecessary merge commits.
  • Use this as a personal guardrail in solo work or as a team standard in collaborative projects.

Quick Start

Follow the rules above when staging and committing in your repository.

Frequently Asked Questions about git-version-control

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

FAQPage Schema
How do I write proper Git commit messages?▼

To prevent unwanted merge commits and maintain clean history, always use git pull --rebase when updating from the remote repository instead of a standard pull command.

What is the best way to stage files in Git?▼

The best way to stage files in Git is to explicitly stage specific files using git add <filename>, strictly avoiding git add -A or git add . to prevent accidental large-scale changes and confusing commits.

Can I use this to enforce Git branching best practices for my team?▼

Yes, you can use this as a team standard in collaborative projects or as a personal guardrail for solo work to enforce proper Git workflow discipline, including branch usage and code reviews.

Why does using git pull --rebase prevent unwanted merge commits?▼

Using git pull --rebase prevents unwanted merge commits by applying your local commits on top of the updated remote branch, avoiding the extra merge commits that a standard pull creates.

When should I not create new Git branches?▼

You should not create new branches or commits unless explicitly instructed, ensuring disciplined commit practices and preventing messy histories in version-controlled repositories.

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
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
masa-codehubmasa-codehub

recording-changes

Stage changes and emit compliant git commit messages with branch validation.

Community
Intermediate
cosmixcosmix
53

git-workflow

Standardize Git branching, commits, and pull request workflows.

Community
Intermediate