Refactor

[samueljoli]

Guidelines

• https://rust-cli-recommendations.sunshowers.io/index.html
• https://clig.dev/#guidelines
• https://smallstep.com/blog/the-poetics-of-cli-command-names/
• https://www.atlassian.com/blog/it-teams/10-design-principles-for-delightful-clis

Spec

• https://github.com/conventional-commits/conventionalcommits.org

Inspo

• https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13
• https://github.com/qoomon/git-conventional-commits
• https://github.com/shobhitpuri/git-refresh?tab=readme-ov-file

[samueljoli]

Blocks: https://github.com/lalilul3lo/baouncer/issues/14

[samueljoli]

Developer dx

In addition to using this library as an executable, it would be nice if users could use this as a git subcommand. Maybe something along the lines of git cc. It turns out that git makes this possible as described here. A couple of things that I need to think about:

• What does a seamless process look like?
• How would this work for a nix user? An example in lakay
• How would this work for a non nix user?
• Implications of having git as an in between. For example surfacing my documentation? I may have to mirror baouncer documentation as git man page.