Is there a document for general coding guidelines for key4hep, specifically Gaudi algorithms?
Stuff like naming conventions, capitalisation, spacing, but also technical things like preference of pointers vs. references or which resource-heavy pitfalls to avoid.
It good place to link this might be the key4hep-doc, e.g. here?
There isn’t a consistent style other than using CamelCase and prefixing member variables with m_. Spacing should be dealt with by formatting (with clang-format, there is a common .clang-format in many repositories but maybe not all of them) and pointers do not have to be used most of the time, although when interacting with other frameworks like DD4hep that use them extensively there is no other way around.
The place you point to would be a good place but we never decided on a consistent style, also ways to enforce them automatically (like for formatting) should be found.