Git Command Finder

How the Git Commands Reference Works

What the Tool Does

The Git Commands Reference provides a searchable, categorized lookup of common git commands organized by workflow: undoing changes, branching, stashing, rebasing, tagging, remote operations, and more. Each entry shows the command syntax, a brief explanation of what it does, and practical usage notes. The search filters entries in real-time as you type, so you can find the right incantation without scrolling through man pages.

Common Developer Use Cases

Developers use this reference when they know what they want to accomplish (e.g., undo the last commit but keep changes staged) but cannot remember the exact flags or command. It is particularly useful for less-frequent operations like interactive rebase, cherry-picking ranges, recovering deleted branches from reflog, or configuring sparse checkouts. Junior developers use it as a learning aid to discover commands they did not know existed.

Data Formats, Types, or Variants

Commands are organized into logical categories: basic operations (add, commit, push, pull), branching and merging, undoing changes (reset, revert, checkout), stashing, rebasing, tagging, remote management, log and inspection, and advanced operations (bisect, worktree, submodule). Each entry includes the command template with placeholder arguments, a one-line description, and relevant flags with their effects.

Common Pitfalls and Edge Cases

Git commands can have destructive effects that are hard to undo — commands like 'git reset --hard' and 'git clean -fd' permanently discard work not saved in the reflog. The reference shows common usage patterns, but git behavior can vary based on configuration (merge.ff, pull.rebase) and git version. Some commands behave differently with and without the '--' separator, especially when filenames collide with branch names.

When to Use This Tool vs Code

Use this reference for quick command lookup during daily development work, especially for operations you perform infrequently. For complex git workflows in production (automated releases, merge queue management, monorepo operations), use purpose-built tooling like git aliases, Husky hooks, or CI scripts that encode your team's specific branching strategy and reduce the chance of human error.