Manage Git version control tasks for EOS code with commit, branch, merge, and push workflows.
npx skills add https://github.com/antonyfmunoz/OS --skill git-antonyfmunoz
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
Git knowledge gaps slow down committing, syncing, and resolving merge conflicts, increasing the risk of broken history or accidental secret commits.
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."
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
dyoshikawaAnalyze git differences and commit history between the current branch and origin main.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
CloudyWingEnforce Git branching, pull request, and release workflows for GitHub or GitLab.
realsigridjinCreate atomic Git commits with conventional formatting and manage repository history.
