git-expert

Inspect Git repository state and plan reversible branching operations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/UntaDotMy/codex_skills --skill git-expert-untadotmy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-expert
Source: https://github.com/UntaDotMy/codex_skills/tree/main/git-expert
Command: npx skills add https://github.com/UntaDotMy/codex_skills --skill git-expert-untadotmy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides safety-first guidance for Git state inspection, branching decisions, and reversible operations to prevent destructive changes.

Core Features & Use Cases

  • State-aware planning: evaluates repository state before writes and suggests safe next steps.
  • Guarded workflows: enforces approvals, patch staging, and review-driven PR hygiene.
  • Recovery & conflict guidance: offers strategies for revert, revert-then-commit, and conflict resolution.

Quick Start

Inspect the current state, request a safe plan, and proceed with explicit approvals.

Frequently Asked Questions about git-expert

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

FAQPage Schema
How do I safely rewrite Git history without losing commits in a shared repository?

To safely rewrite Git history, you need an audit-ready plan with explicit approvals and preflight checks. This approach evaluates repository state and provides guarded workflows to ensure operations remain reversible and prevent destructive changes.

What's the best way to resolve Git merge conflicts without breaking the branch?

Resolving Git merge conflicts safely requires state-aware recommendations and patch staging. By evaluating the repository state first, you can apply conflict resolution strategies that maintain branch integrity and prevent accidental data loss.

How do I recover a deleted Git branch or undo a bad commit?

Recovering a deleted Git branch or undoing a commit involves reversible operations like revert and revert-then-commit. This approach provides recovery guidance grounded in your current repository state, ensuring changes are safe and auditable.

Can I enforce PR hygiene and approvals before pushing changes to a remote repository?

Yes, you can enforce PR hygiene and approvals before pushing. Guarded workflows apply review-driven patch staging and require explicit approvals, ensuring that all changes to shared repositories are carefully planned and safe.

Why should I run preflight checks like git status and git diff before branching?

Running preflight checks like git status and git diff before branching ensures safe state inspection. This state-aware planning evaluates your current repository condition to suggest safe next steps and prevent destructive changes.

Does this Git safety guidance work for local repositories or only shared ones?

This Git safety guidance applies to both local and shared repositories. It delivers state-aware recommendations and guardrails for history rewriting, ensuring careful planning and explicit approvals regardless of the repository type.