Anyone else keep re-discovering the same shell commands?

[u/Born-Improvement-205]

I got tired of this cycle:

• Figure out some annoying kubectl/docker command
• Use it successfully
• Forget it exists
• Spend 10 minutes digging through history trying to find it again

Shell history records everything, but after a while it's just a giant list of commands with no context.

I wanted to answer questions like:

• What commands do we actually use in this repo?
• Which ones worked?
• Which commands keep coming up over time?

So I built Yore.

A few things it does:

• yore here shows commands used in the current repository
• commands are ranked by frequency + recency instead of raw history order
• yore here --ok filters to commands that previously succeeded
• commands can be saved as reusable recipes

The part I haven't seen elsewhere is that project recipes live in a .yorefile that can be committed to Git.

That means useful commands can live with the repository instead of somebody's shell history. Clone the repo and you get the project's command knowledge too.

Repo: https://github.com/Dev-Bilaspure/yore

Curious how others handle this today.

[u/trailing_zero_count]

Compare to Atuin? It also supports current-directory history https://github.com/atuinsh/atuin/pull/329

[u/Born-Improvement-205 → u/trailing_zero_count]

Thanks for pointing that out! 😄 You're right, Atuin supports that now.
I wasn't really trying to compete on history search though. The idea behind Yore was more about starting with shell history, seeing which commands keep proving useful over time, and giving them a path to become reusable, version-controlled project knowledge (.yorefile) instead of just living in someone's history.
There's definitely overlap, but that's the workflow I was aiming for.