With a 2,000 page bill, it would make it easier to keep up with the changes, even if you don't yet know what is in every page at the start.
In College, I did spend some time wondering if a good Robert's Rules meeting running software might be a generally useful project, after being in a few society meetings where branches got long and twisty (amendment to an amendment to a proposal type things). Never did build anything more than a prototype though.
Seek out Thomas Jefferson's Manual for those clubs you'd like to see thrive. It promotes fraternity. https://en.wikipedia.org/wiki/Jefferson%27s_Manual
It would be an interesting project. Particularly if you could also wrap up the git in an interface that's accessible to non-programmers.
As far as the US goes, the Federal Register is a good place to start to see things as they happen.
What I think is missing is a concept of document: commits (laws) just accumulate on top of each other without producing named, organized documents (files, in proper source control systems) with clear responsibilities, that can be easily referred to from other documents, and of which the latest version is the only one that counts.
Instead, when you want to read a computer program, you don't look at individual commits to the code base, you look at its files. Commits are more or less irrelevant, what counts is the most recent version of a set of documents, and each commit might create, modify or delete more than one document.
It seems only a change in perspective, the end result is the same; but reasoning in terms of documents with well-organised names and responsibilities, describing processes and data and designed for reusability, is much easier and more compact.
It's still full of references to bills and such, but it is the consolidated text of the law.
has lots of intersting proposals and attempts