You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,3 +8,5 @@ The documentation is located here: https://jaredmales.github.io/mxlib-doc/
8
8
9
9
See the [User's Guide](https://jaredmales.github.io/mxlib-doc/modules.html) for [installation instructions](https://jaredmales.github.io/mxlib-doc/group__installation.html)
10
10
11
+
See the [Testing](https://jaredmales.github.io/mxlib-doc/group__mxlib__testing.html)
12
+
section for test build, test execution, and coverage instructions.
- When renaming members/APIs, update all dependent call sites.
40
+
- Keep changes minimal and scoped.
41
+
42
+
8) Formatting and Verification
43
+
- Run `clang-format` on touched files.
44
+
- Ensure docs and naming are consistent after formatting.
45
+
- Report any places where project style is ambiguous before making assumptions.
46
+
47
+
9) Doxygen Named Section Ordering
48
+
- For classes that expose configuration via member data + accessors, keep named sections split into:
49
+
-`... - Data` for protected/private member state
50
+
-`...` (without `- Data`) for public access functions
51
+
- Place the `... - Data` section before the corresponding public accessor section.
52
+
53
+
10) Header Declaration Parameter Docs
54
+
- In headers, prefer inline parameter documentation on declarations (`type name /**< ... */`) rather than separate `\param` lists, unless there is a specific reason to deviate.
55
+
56
+
11) PR Prompt Attribution
57
+
- At the top of PR descriptions, include an explicit attribution line when work was performed with Codex.
58
+
- Preferred format:
59
+
-`This work was performed by GPT-5.3-Codex in response to the prompt: "...".`
60
+
- Include the primary user prompt verbatim (or a faithful condensed version if it is extremely long).
61
+
62
+
When you finish:
63
+
- Summarize what changed.
64
+
- List affected files.
65
+
- Note any follow-up items or potential edge cases.
0 commit comments