13 Advanced (but useful) Git Techniques and Shortcuts

Git productivity often comes down to avoiding the two classic disasters: committing the wrong thing (or with the wrong message) and then trying to fix it after the fact. The most practical theme running through these “advanced but useful” techniques is that Git gives you surgical control over history and working state—so you can recover quickly without turning every mistake into a multi-hour debugging session.

A fast workflow starts with skipping redundant steps. Instead of running `git add` and then `git commit`, the `-a` (am) flag lets `git commit -a` automatically stage changes in the current working directory. For even more speed, Git aliases can compress longer commands into short custom shortcuts (for example, an `ac` alias that performs add+commit). When speed causes errors, `--amend` becomes the safety net: it updates the latest commit with a corrected commit message or missing/staged files. If the commit message needs to stay the same, `--no-edit` preserves it. But amending after pushing requires caution—using `git push --force` overwrites the remote branch with the amended local state, and any remote-only commits can be lost.

When the wrong code has already been pushed and should be undone without rewriting history, `git revert` provides a cleaner rollback. It creates a new commit that returns the repository to the state of a chosen earlier commit, leaving the original commit in history. For situations where local access isn’t available, GitHub’s web-based editing and GitHub Codespaces let developers make changes and submit pull requests from a browser or cloud VS Code environment.

To manage work-in-progress safely, `git stash` temporarily removes changes from the working directory while keeping them for later. Stashes can be named (`git stash save <name>`), listed (`git stash list`), and restored (`git stash apply <index>`), which is especially useful when experiments would otherwise block committing stable code.

The transcript also targets day-to-day repo hygiene and debugging. It notes the modern default-branch naming shift away from `master` toward `main` (or other names), and it improves commit history readability with `git log --graph --oneline --decorate`. For pinpointing the exact commit that introduced a bug, `git bisect` performs a binary search between a known-good commit and a suspected bad range, using `git bisect good` as you validate each step.

For cleaner pull requests, interactive rebasing enables commit squashing. Using `git rebase -i` on the target branch brings up a list of commits where `pick`, `reword`, `squash`, and `fixup` control what happens to each commit. Auto-squash options can preconfigure squashing behavior when commits were created with `--fixup`.

Finally, the transcript covers automation and cleanup. Git hooks let developers run scripts before or after Git events; `husky` is highlighted as a common way to set up JavaScript-friendly hooks. For recovery from a bad local state, `git fetch` followed by `git reset --hard` restores the local branch to match the remote, and `git clean` removes leftover untracked files/build artifacts. If Git is no longer desired, deleting the hidden `.git` directory effectively resets the project to non-Git status. A quick navigation shortcut—`git checkout -`—returns to the previous branch after switching. Together, these techniques aim to make Git feel less like a trap and more like a set of reliable tools for editing, debugging, and maintaining history.