git

Name: git
Availability: InStock
Author: antonyfmunoz

Manage Git version control tasks for EOS code with commit, branch, merge, and push workflows.

1|Updated Mar 11, 2026

Search Tags:#git #version control #code history #branching #merge conflicts #github sync #commit workflow

Ready to run

npx skills add https://github.com/antonyfmunoz/OS --skill git-antonyfmunoz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/git
Command: npx skills add https://github.com/antonyfmunoz/OS --skill git-antonyfmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git knowledge gaps slow down committing, syncing, and resolving merge conflicts, increasing the risk of broken history or accidental secret commits.

Core Features & Use Cases

Main-only EOS workflow: Commit directly to main for day-to-day work while reserving feature branches for experimental changes.
Safe commit hygiene: Enforces EOS commit message style and avoids dangerous staging commands that could leak secrets.
Conflict diagnosis and recovery: Provides practical commands for checking status, reviewing diffs, resolving conflicts, and recovering lost work via reflog.

Quick Start

Tell the AI: "Use git to stage only the specific files I changed in /opt/OS, create a commit with an EOS-style lowercase imperative message, and push to origin main."

Frequently Asked Questions about git

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

FAQPage Schema

What is the best way to resolve git merge conflicts and recover lost commits?▼

The best way to resolve git merge conflicts is to review diffs and check repository status before staging. You can recover lost commits by inspecting the reflog to find previous repository states safely.

How do I create safe git commits without leaking secrets or breaking history?▼

To create safe git commits, stage only specific changed files rather than using broad staging commands. This disciplined staging approach prevents accidental secret commits and maintains atomic history.

When do I need to use feature branches in a main-only development workflow?▼

In a main-only development workflow, you commit directly to main for day-to-day work and reserve feature branches only for experimental changes, simplifying version control while keeping your primary codebase stable.

How do I synchronize code and push commits across multiple devices using git?▼

You synchronize code across devices by using reliable push and pull workflows to sync your local repository with a remote origin, ensuring your commit history and branch states remain consistent.

Why does my git commit workflow require lowercase imperative messages?▼

Your git commit workflow requires lowercase imperative messages to enforce consistent commit hygiene and history inspection standards, making it easier to parse atomic commits and track code changes.

What are the limitations of committing directly to main for day-to-day version control?▼

Committing directly to main limits isolated testing since experimental changes require branching. To avoid broken history, you must enforce strict commit hygiene and avoid staging commands that could leak secrets.