GP Saggese

@sonniki how about we use this issue as a catch all issues posting examples of what needs to be automated in code reviews In llm_transform.py I have a bunch of...

FYI, when I see a PR that has a problem with our style, I check out the branch, and implement the filters directly in llm_transform and fix them with LLM,...

Let's use that document as the official reference for humans and machines. We'll move things little by little to llm_transform.py / ai_reviewer.py to automate and delegate the effort to the...

From https://github.com/ehaabbasil/helpers/issues/1 - **Task**: - We want to create a graph for`helpers` to understand import dependencies and improve `helpers/import_check` - We want to ensure there are no circular dependencies -...

@ehaabbasil can you pls go through https://github.com/causify-ai/helpers/pull/660 and fix the TODOs? Also re-reading some of the docs can help. I'll file a bug for it

Arch changes after another round of review 1) We want to use the same approach as the other scripts detect_import_cycles.py, show_imports.py) - There is a script that does the work...

Once everything is ready, we want to send an email to the team, like it was a release, with - an explanation of how to use is (pointing to the...

Coverage (since it is in that in that EPIC), but let me update the title for clarity. But, good point, yes, we should start doing releases and send an email...

Correct. The invariant is that the "dev system paper" is like a white paper that describes at high level how we develop. When somebody new joins, they read that paper...

Yes. I've converted the latest md paper to latex.