Instead of depending entirely on documents shared in groups, you can create a commands list directly from the bot you use.
This is generally the best way to make sure your reference matches your installed application.
You do not need advanced programming knowledge.
You only need access to the bot menu and a document editing application.
Step 1: Open Your Actual WhatsApp Bot
Start by opening the WhatsApp conversation or group where your bot is available.
Make sure you are using the correct project.
If you use multiple bots, identify which one you want to document.
Do not begin with a commands list downloaded from another source.
Step 2: Run the Menu or Help Command
Find the menu or help command documented by your bot.
Enter it using the correct prefix.
The bot should display its available command categories if that functionality is supported.
Some projects use different menu commands, so check the bot's instructions if you are unsure.
Step 3: Copy the Available Categories
Read the menu carefully.
Write down the categories displayed by your bot.
For example, your list might include:
Menu and help.
Group management.
Media tools.
Entertainment.
Utility.
AI.
Owner.
Only include categories that actually appear in your bot.
Do not add categories simply because another project supports them.
Step 4: Copy the Actual Commands
Open each category and record its documented commands.
Where possible, include a short explanation of each command.
For example, a generic entry could look like this:
Example command: A command that displays information about the current group.
This avoids inventing command names or including unsupported features.
If the bot provides usage examples, copy them accurately.
Step 5: Write the Correct Prefix at the Top
The prefix should be clearly visible near the beginning of the document.
This is important because users may otherwise copy a command using the wrong symbol.
If your bot allows its prefix to be changed, make sure the PDF reflects the current configuration.
Step 6: Add the Bot Name
Clearly identify the bot described in the document.
If the project has a version number, include it.
If the version is unknown, do not invent one.
You can simply write that the version was not specified.
Step 7: Add the Document Date
Write the date when you collected the commands.
This helps readers understand when the information was last checked.
For example, a document could contain:
Bot Name: Your installed bot name
Prefix: Your configured prefix
Version: As displayed by the project, if known
Prepared On: The date you created the document
Step 8: Organize Everything Into a Document
Open a notes application or document editor.
Create a clear heading for each command category.
Under each heading, include:
Command name.
Short description.
Required permission, if documented.
Usage instructions, if available.
Avoid putting everything into one large paragraph.
A properly organized document is easier to read on a smartphone.
Step 9: Review the Information
Before exporting, compare the document with the bot menu again.
Check spelling, prefixes, command names, and permission information.
Remove any commands that you could not verify.
If a feature is unavailable or undocumented, do not present it as a working command.
Step 10: Export or Print as PDF
When the document is ready, use the export or print option in your editing application to create a PDF.
Save it with a clear file name.
For example, you could use the bot name and preparation date as the document title.
You now have a personal commands list that is based on your actual bot rather than an unrelated online reference.