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: documentation/create_code_doc/prompts/structured_doc.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -32,5 +32,5 @@ This is particularly helpful for libraries or tools meant to be used by other de
32
32
33
33
-When documenting, aim for clarity, brevity, and completeness. Remember, the primary goal is to make the code as understandable and usable as possible for anyone who encounters it in the future.
34
34
35
-
Using the guidelines above create documentation for code provided below without mentioning any of the guidelines above in documentation and only include required sections in documentation, never have empty sections:
35
+
Using the guidelines above create documentation for code provided below without mentioning any of the guidelines above in documentation and only include required sections in documentation, never have empty sections. The output should be markdown, without markdown code block that can be directly used without any changes and any additional content:
0 commit comments