frecenfile

Once you have a little frecency command-line utility like https://github.com/c-blake/adix/blob/master/util/lfreq.nim (inspired by this very HN thread!) and then either fzf, vip (https://github.com/c-blake/bu/blob/main/doc/vip.md), or whatever, the essence of the idea is really just two lines of Zsh code (https://github.com/c-blake/bu/blob/main/doc/vip.md#combining...). It's only a couple dozen more to have a more robust/complete system, though with shared-across-shells PWD histories and long-term saving somewhere with lock files. As another example of why a simple CL utility for frecency alone is nice, you can basically replicate https://github.com/kantord/frecenfile with a shell 1-liner: git log --pretty=format: --name-only | tac | sed '/^$/d' | lfreq -n9 -o.999 In a little timing test I did this morning, that was about 270X faster

frecenfile is a tiny CLI tool written in Rust that analyzes your Git commit history in order to identify "hot" or "trending" files using a frecency score that incorporates both the frequency and recency of edits. It is fast enough to get an instant response in most repositories, and you will get a reasonably fast response in practically any repository. It can be useful for getting a list of "recent"/important files when Git history is the only "usage" history you have available.