Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using LLM to improve documentation #563

Open
keceli opened this issue Dec 8, 2024 · 1 comment
Open

Using LLM to improve documentation #563

keceli opened this issue Dec 8, 2024 · 1 comment

Comments

@keceli
Copy link
Contributor

keceli commented Dec 8, 2024

I recently wrote a Python script that leverages GPT4o via Argonne's OpenAI service, Argo, to improve our documentation. The script focuses on fixing grammar and formatting issues while also improving the overall clarity of the content. Using this script, I have submitted PRs (#504, #562, #564) with updated documentation for review. I am creating this issue so we can have some of the more general discussion here rather than in the PRs.

  1. Are there any concerns about the use of LLMs?
  2. Are there any specific improvements or changes to the script and the prompts you’d suggest?
  3. Is it worth automating this process further (e.g., integrating it into a GitHub action for automated checks)?
  4. Should I continue submitting PRs in this way for the rest of the documentation?
  5. Are the PR sizes appropriate?

For 3, I already wrote a script, but it requires an OpenAI API key. Would ALCF provide one for this service or should we try free models that can run on GitHub CI servers? Alternative is to have a mirror of the repo on GitLab and run GitLab action on ALCF machines with Argo access. Is this a viable approach?

Prompt

 Your task is to:

1. Identify and correct any grammatical errors.
2. Check for and fix any broken links.
3. Address any formatting issues.
7. Do not modify anchors within headers.
8. Provide a brief explanation of the changes made.
9. If no changes are necessary, respond with "The page reads great, no changes required."
10. If any change is required your response should include
    1. The revised content of the markdown file.
    2. An explanation of your changes, after adding this separator {separator}.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant