A field guide to version control

GitAtlas

Every Git and GitHub command worth knowing — written in plain English, with the situation you would actually reach for it in, and a copy button on all of them.

381commands 26sections 80worked examples

~/projects/myapp main

Emergency Response & Hardening

Git Security & Secret Shield

Scan diffs for leaked API keys, purge credentials from Git history safely without corrupting repositories, generate pre-commit shields, and follow an incident recovery checklist.

Paste Commit Diff, Code Snippet, or .env

Test Sample Leaks:

100% Privacy-Preserving: All regular expression evaluations happen entirely inside your browser JavaScript runtime. Nothing is transmitted over any network.

Scan Results

Paste a commit diff, code snippet, or .env file on the left to scan for leaked secrets.

Pre-Commit Secret Shield Hook

A lightweight bash script that executes automatically before every git commit. It inspects all staged files and aborts the commit if an .env file, cryptographic key, or token pattern is detected.

Hook Implementation Format

Hook Script Preview

Leaked Secret Incident Remediation Checklist

Follow these 7 critical steps in order if credentials were pushed to GitHub or a shared remote. Checkboxes persist across page reloads.

1. Invalidate & Revoke the Exposed Credential Immediately

Go to your cloud dashboard (AWS IAM, Stripe, OpenAI, GitHub PATs) and delete/roll the key. Once a secret is pushed, treat it as compromised forever.

2. Audit Activity & Billing Logs

Review AWS CloudTrail, Stripe Event Logs, or database query logs for suspicious API requests or unexpected infrastructure spikes made during the exposure window.

3. Scrub History using git-filter-repo

Run git filter-repo --invert-paths --path <secret-file> to purge all historical commit references, trees, and blobs across all branches.

4. Force-Push Cleaned History with Lease

Execute git push origin --force-with-lease --all and git push origin --force-with-lease --tags to update remote refs safely.

5. Clear GitHub Commit Cache & Orphan Pull Request Refs

If the repository is public, contact GitHub Support to purge unreachable cached commit SHAs, or delete associated PR heads if feasible.

6. Add Pattern to .gitignore and Install Pre-Commit Hook

Ensure .env, *.pem, and *.key rules are committed to .gitignore, and install the GitAtlas Pre-Commit Shield.

7. Coordinate with Team Members

Instruct collaborators to re-clone the sanitized repository or run git fetch origin && git reset --hard origin/main to avoid re-pushing dirty history.

Visual Sandbox & DAG Simulator

Interactive Git Graph & Branch Visualizer

Watch how branches, commit hashes, HEAD pointers, and merge commits move before you run commands in your terminal. Choose a guided scenario or test freely in sandbox mode.

git merge (3-Way Merge)

Joining divergent branches by creating a merge commit with two parents.

Step 1 of 3

Initial State: Divergent Branches

Terminal Command

$ git checkout main

Under the Hood

You are on the "main" branch. Both "main" and "feat/login" have new commits that branched off commit C2.

💡

Notice C3 and C4 on "feat/login", and C5 on "main". Both have progressed independently.

main feature rebased cherry-picked orphan / undone

Terminal & Command Line Companion

GitAtlas in Your Terminal

Search 381+ commands, diagnose errors, and scan for secrets directly from your command line with zero installation required.

Zero Install

Run Instantly with NPX

Execute queries on the fly without installing anything globally:

npx gitatlas <search query>

Native Git

Native Git Alias (`git atlas`)

Add a 1-line alias so you can type git atlas <query> natively in Git:

git config --global alias.atlas "!npx gitatlas"

Shell Function

Bash / Zsh / PowerShell Shortcut

Drop this snippet into your ~/.zshrc, ~/.bashrc, or $PROFILE:

gitatlas() { npx -y gitatlas "$@"; }

terminal ~ (gitatlas-companion)

$ npx gitatlas undo commit

◆ GitAtlas CLI — The Field Guide to Git

➔ git reset --soft HEAD~1 Removes the last commit but leaves all its changes staged. Risk: Safe (Local only)

➔ git revert HEAD Creates a brand-new commit that undoes the changes of a previous one. Risk: Safe (Preserves history)

$ git atlas --fix "rejected"

🚨 Error: Updates were rejected because the remote contains work Safe Fix: Pull first with rebase, then push — never force push on shared branches. $ git pull --rebase origin main && git push

Interactive Studio

Build, simulate & compose.

Visually configure complex multi-flag commands, simulate safe recovery paths, generate tailored .gitignore rules, and draft conventional commits with instant one-tap copy.

Display & Formatting Preset

Branch Scope

Commit Limit

Author Filter

Date Range

File or Directory Path

Search Commit Message (--grep)

Merge Commits

Generated Command

git log --graph --oneline --decorate --all -n 10

Flag Breakdown

Step 1

Where are the changes right now?

Step 2

What is your goal?

Recommended Command Safe

git restore path/to/file.js

Why this command?

Quick Presets

Custom Rules (Appended at bottom)

File Preview

Type

Scope (optional)

Short Description (imperative mood)

💥 Breaking Change! (Appends ! to header)

Extended Body (optional)

Issue Footer (optional)

Runnable Command

git commit -m "feat: add user avatar upload endpoint" -m "Closes #42"

Message Preview

Guided recovery

Not sure what to run next?

Answer two questions and GitAtlas hands you an ordered playbook — with the read-only check to run before every risky step, and what each one cannot be undone from.

Or open a playbook directly

Troubleshoot safely

Paste the Git error you hit.

GitAtlas matches common errors locally, then gives you a plain-English cause, safe checks, and the next command to run. Nothing you paste leaves this page.