git

Guide Git staging, commits, branching, and pull request workflows.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/oornnery/skills --skill git-oornnery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/oornnery/skills/tree/main/skills/git
Command: npx skills add https://github.com/oornnery/skills --skill git-oornnery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git workflows can be error-prone, risky, and hard to audit; this skill provides safety guidelines, proven patterns, and a cohesive way to manage branches, commits, PRs, and recover from tricky git scenarios.

Core Features & Use Cases

  • Safe staging and commit practices: stage by file to avoid accidental broad changes
  • Branching and PR guidance: recommended workflows, rebasing vs merging, and release tagging
  • Worktree and bisect support: safe parallel work and regression identification

Quick Start

Review your changes, stage by file, commit with a precise message, and verify before pushing

Frequently Asked Questions about git

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

FAQPage Schema
What is the safest way to stage and commit changes in git?

Safe git staging involves adding changes by individual file rather than broadly staging all modifications. This practice prevents accidental commits and ensures precise commit messages, improving overall workflow auditability and reducing risk before pushing.

How do I choose between rebasing and merging for my pull request?

Choosing between rebasing and merging depends on your branching workflow and release tagging strategy. Rebasing maintains a linear history, while merging preserves context; safe git practices guide this decision based on your specific code review and release needs.

When do I need to use git worktree for parallel work?

Git worktree is needed for safe parallel work when managing multiple branches simultaneously without cluttering a single working directory. It allows developers to perform feature work, code reviews, and releases concurrently in isolated directory paths.

How do I identify a regression using git bisect?

Git bisect identifies regressions by binary searching through commit history to locate the exact change that introduced a bug. This workflow supports recovery from tricky git situations by systematically narrowing down problematic commits.

Can I recover from tricky git situations like bad commits or branches?

Recovery from tricky git situations is supported through proven patterns and core safety rules. The skill guides developers through complex recovery scenarios including bad commits, branching errors, and regression identification using bisect workflows.