The help text became a pull request
u/dizzygoldfish asked a Grok Bot to write help pages for uploading a csv file. The writing was bad. After the complaint the bot rewrote it and pushed a pull request. He spent a day on rules in a git repo.
Done with Grok BotAdvanced
What was done
On 27 August 2026 u/dizzygoldfish writes that he spent a couple of days starting Grok Bot. He connected it to a personal data store he had built for a local assistant. The personal part was fine, and he liked that a larger model came with the Cursor subscription. What he wanted was help with product copy, marketing and specifications. That did not work. He asked the marketing bot to write help pages for uploading a csv file into their system. The writing was bad. He asked it to revise, and said that a wall of random text did not help. The bot rewrote the text and pushed a pull request. He spent a whole day writing rules in a git repo to control the output.
How it went
The pull request was pushed after he rejected the first draft. He does not say it was merged, or that the text became usable.
Worth knowing
The help text is not quoted. The repo is not named. He does not say the rules he wrote that day stopped the next pull request.
How to do it
- Ask for a draft of the help page, and read it against what the screen actually does.
- If the text is unusable, say what is missing, and ask for a new draft.
- Commit the change yourself. Do not let the bot open a pull request until you have said yes.
Try it with Grok Bot
Write a draft help page for [task] in [product]. Do not open a pull request and do not publish the page until I say yes.
Replace text in brackets with your own.
Done when. The draft has been read, and no pull request has been opened without a yes.
Safety rule. No pull request and no publish until you have said yes.
Read the original
Read the original · u/dizzygoldfish on Reddit ·