[Documentation] Encode rules for skeleton, asserts, unrecheable, testing, etc

[bcardosolopes]

Inspired by @Lancern work on providing some ASM guideline goodness, I created some guidelines for auto and camelCase usage, see it here: https://llvm.github.io/clangir/GettingStarted/coding-guideline.html

However, we still need to encode the other common review items, such as OG skeleton, asserts, unrecheable, testing, etc. It'd be nice to have that.

[bcardosolopes]

cc: @sitio-couto @seven-mile @gitoleg @orbiri @jopperm

[eZWALT]

Inspired by @Lancern work on providing some ASM guideline goodness, I created some guidelines for auto and camelCase usage, see it here: https://llvm.github.io/clangir/GettingStarted/coding-guideline.html

However, we still need to encode the other common review items, such as OG skeleton, asserts, unrecheable, testing, etc. It'd be nice to have that.

Would it make sense If I presented a proposal of Dialect intermixing guidelines? I'm guessing it could be useful for other future contributors which for instance, might want to tackle OpenACC.

[bcardosolopes]

That'd be great