skills.rest
SimonOneNineEight
SimonOneNineEightCOMMUNITY
Explore all skills by this author →
GitHub

Git

Provides guidance for non-destructive Git workflows across commits, branches, merges, and pull requests.

Updated Apr 4, 2026
Search Tags:#git#branching#merging#pull-requests#version-control#rebasing
One-click install
npx skills add https://github.com/SimonOneNineEight/openclaw --skill git-simononenineeight
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git
Source: https://github.com/SimonOneNineEight/openclaw/tree/main/workspace/skills/git
Command: npx skills add https://github.com/SimonOneNineEight/openclaw --skill git-simononenineeight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates best practices for Git operations to prevent common history-tampering mistakes, reduce conflicts, and improve collaboration and traceability.

Core Features & Use Cases

  • Stateless safety discipline: promotes non-destructive workflows like pull before push, feature-branch hygiene, and safe rebasing strategies.
  • Team collaboration and recovery: provides guidance on conflict resolution, reverts, and history recovery to minimize disruption.
  • Use Case: When a team collaborates on a repository, this skill helps maintain clean history, consistent commit messages, and safe merging practices.

Quick Start

Initialize a new Git repository with safe defaults and create an initial commit

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 maintain a clean Git history when collaborating?▼

Safe Git workflows enforce pulling before pushing, feature-branch hygiene, and consistent commit messages to maintain a clean, auditable project history and reduce conflicts during team collaboration.

How do I resolve Git merge conflicts without losing changes?▼

Resolve Git merge conflicts safely using non-destructive workflows that prioritize history recovery and reverts, minimizing disruption while ensuring both sets of changes are auditable before completing the merge.

When should I use Git rebasing instead of merging?▼

Use Git rebasing to maintain a linear project history, applying safe rebasing strategies to avoid history-tampering mistakes, whereas merging preserves the exact chronological context of branch development.

Does this Git workflow guidance prevent force-push on shared branches?▼

Yes, these Git workflows enforce specific guardrails to prevent force-push on shared branches, protecting the collaborative project history from destructive overwrites and history-tampering mistakes.

How do I initialize a new Git repository with safe defaults?▼

Initialize a new Git repository with safe defaults by setting up non-destructive rules from the start, then creating an initial commit to establish a clean, auditable baseline for future history.

Why should I pull before push in Git?▼

Pulling before pushing in Git is a stateless safety discipline that prevents history-tampering mistakes, ensures your local branch is synchronized, and reduces the likelihood of push rejections and 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
oborchersoborchers
28

tag-based-production-deploys

Enforce git tag-based production deployments with manual approval gates.

Community
Advanced
HenquewlHenquewl
7

finishing-a-development-branch

Verify test suites and finalize git development branches through merge or cleanup.

Community
Advanced
JitsusamaJitsusama
6

git-hygiene

Enforce atomic Git commits and safe history rewriting practices.

Community
Basic