You should group your source files by domain, then by feature, e.g. ‘src/foo/model’ and ‘src/foo/exports’.

Is serialization/deserialization the only aim of these structures ? If not, that code should definitely be separated, so as to evolve separately from the structure itself.

If it is the only aim, the code should also be separated, so you can change your serialization type (e.g. from JSON to XML) without impacting the model.

Also you might need another export for compatibility with another software, and you don’t want your model file to grow with the 10 formats you support.

but it started splitting my commits in chunks

Wait, it can split commits ? I thought you “just” used a LLM to write the messages, but it can also act on the commits ?

How did you achieve this?

I’m really curious to see examples of commit messages.

And more details on how you achieved it, I’d like to give it a go myself, as some of my coworkers commit messages are less than stellar.

Does it write in the conventional commit formalism ?