jj is built on top of Git. If you use “colocated” repositories (which is now the default), your Git workflows will still work. In fact, all my Nvim setup with Git plugins didn’t need any change. When your run jj commands, they will operate on the Git repo, and if you run Git commands, they will be imported by jj as needed. I’ve been using almost exclusively jj at work and in open-source contributions, and so far no one has noticed (why should they).

As to why you should use it, let’s say that it encourages you to have a better development workflow, a cleaner Git history, and an easier time working on top of code that is being reviewed, by lowering the barrier. Rebase is easier to use, absorb and squash are a godsend for keeping a clean history, and a lot of design decisions that, when you think about it, just makes sense from a usability perspective.

I encourage you trying it out, I certainly don’t regret it, it does feel a lot easier to use than bare Git.