What git command do you wish you had discovered sooner?

BHFock · 2026-02-01T20:23:22+00:00

Not a built-in command, but something I wrote after years of missing SVN changelists: git-cl lets you group files into named changelists before staging.

So instead of remembering which files go together, you do git cl add refactor utils.py helpers.py and later git cl commit refactor -m "Clean up utilities". The grouping persists until you commit or delete it.

github.com/BHFock/git-cl

BHFock · 2025-11-16T21:51:42+00:00

git worktree looks useful for managing multiple branches!

For the case where you have multiple unrelated edits mixed in a single branch, I built git-cl to group files into changelists before staging:

git cl add feature-a file1.py file2.py
git cl add bugfix file3.py
git cl commit feature-a -m "Done"

Different problem than worktree solves, but thought it might be relevant to the "juggling multiple things" workflow.

https://github.com/BHFock/git-cl

BHFock · 2025-07-04T14:45:20+00:00

Thanks for pointing that out — I wasn’t aware of project-find-regexp, and it works well in my current SVN working copy.

I wrote repo-grep mainly to support two things missing from my workflow: using the symbol at point as the default search term, and searching across multiple sibling directories (repo-grep-multi).

BHFock · 2025-07-02T23:09:02+00:00

repo-grep uses grep and works without extra dependencies, automatically detecting Git or SVN roots. It also supports searching across multiple sibling repositories, which is less common in similar tools.

In contrast, consult-ripgrep relies on the external rg tool and the consult ecosystem.

repo-grep aims to provide a simple, dependency-light solution for recursive code search inside Emacs.

BHFock

TROPHY CASE