Add Conventions and Agent Instructions documentations - #90
Conversation
|
🎯 Code Coverage (details) 🔗 Commit SHA: 7deae76 | Docs | View more details | Give us feedback! |
| - Keep functions small and focused (<~ 20 lines when practical). | ||
| - When practical, place caller functions before callees, so the code can be read from top to bottom. | ||
|
|
||
| ## C++ Code Style |
There was a problem hiding this comment.
If these could be expressed in clang-format and clang-tidy. Then lets do it that way.
LLMs are awesome, but detereministic rules are even better :D
There was a problem hiding this comment.
For sure!
I think doing so should be done in a dedicated PR, because it could imply correcting existing code.
pawelchcki
left a comment
There was a problem hiding this comment.
One suggestion about using clang-tidy and format. Instead of relying on LLMs promise to follow the rules :D
Other than this looks good to me the
|
I think its worth keeping in mind that AGENT.md rules - with newer LLMs might need trimming. |
This PR:
This was done taking as an example what was recently done in
dd-trace-cpp: Readme, Security, Contributing, Conventions, Claude, Agents.Jira ticket: IDML-772 [Apache] Add conventions and agents documentation