super man page with AI-assisted tooling to generate/maintain#6824
Open
super man page with AI-assisted tooling to generate/maintain#6824
Conversation
1fd608e to
427b51a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's Changing
This adds a man page for
superthat can be included in our release artifacts and installed as part ofbrew install super. The approach uses Claude AI to generate the page from the output ofsuper -hand selectbook/docs.Why
It's been pointed out that some developers might look for a man page rather than jumping right to https://superdb.org or relying on the brief
super -houtput. While man pages are not as heavily relied upon as in the past, their presence or absence may be seen as an indicator of a tool's maturity.Details
The README gives more detail on the usage and approach. In brief, I was nervous at the thought of having yet another set of docs to keep in sync, hence the attempt to use AI. The semi-automated approach here can become an additional step right before tagging the release to make sure the man page is still current: When run, material changes to the upstream sources will be obvious as diffs in the
super.1.md. With minimal human effort, these changes be incorporated into the committed man page source.Credit
Thanks to Gilles Clement for floating the idea, creating the first draft of the prompt, and showing how an LLM could generate a decent man page for us.