git-essentials

Provide Git commands for branching, merging, rebasing, and conflict resolution.

23|2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/asgarovf/locusai --skill git-essentials-asgarovf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-essentials
Source: https://github.com/asgarovf/locusai/tree/main/skills/git-essentials
Command: npx skills add https://github.com/asgarovf/locusai --skill git-essentials-asgarovf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive guidance and commands for complex Git operations, helping users navigate branching, merging, rebasing, and conflict resolution efficiently.

Core Features & Use Cases

  • Branch Management: Create, name, and maintain feature, fix, and release branches according to best practices.
  • Conflict Resolution: Offers strategies and commands to effectively resolve merge and rebase conflicts.
  • History Management: Assists in cleaning up commit history using interactive rebase and provides tools for investigating past changes.
  • Recovery: Guides users on how to recover from mistakes using git reset, git revert, and git reflog.
  • Use Case: When encountering a merge conflict during a rebase, use this skill to understand the conflict and apply the correct resolution steps.

Quick Start

Use the git-essentials skill to create a new feature branch named 'feat/123-add-user-auth' from the main branch.

Frequently Asked Questions about git-essentials

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

FAQPage Schema
How do I resolve a merge conflict during a git rebase?

To resolve a merge conflict during a git rebase, you must manually edit the conflicting files to keep the desired changes, stage the resolved files, and continue the rebase. This skill provides strategies and commands to effectively resolve these conflicts.

What is the best way to recover a deleted branch using git reflog?

Git reflog records a history of reference updates, allowing you to find the commit hash of your deleted branch. You can recover the branch by running git reset --hard <commit-hash> to restore your repository state to that specific point.

How do I clean up commit history with interactive rebase?

You clean up commit history with interactive rebase by squashing, rewording, or dropping commits to ensure atomic commits. This skill assists in cleaning up commit history using interactive rebase for a more readable project timeline.

When should I use git reset versus git revert to undo changes?

Use git reset to move your branch pointer backward and discard commits locally, while git revert creates a new commit that undoes previous changes. This skill guides users on recovery methods using reset, revert, and reflog to avoid rewriting shared history.

What are the standard git branch naming conventions for feature and fix branches?

Standard git branch naming conventions typically use prefixes like 'feat/' for features and 'fix/' for fixes, often including an issue number. This skill helps create and maintain branches according to these best practices, such as 'feat/123-add-user-auth'.