Docs: Add comprehensive Social Media Integration Guide

[firaseth]

📝 Integration Guide Update

This PR adds a comprehensive Social Media Integration Guide to the documentation, covering platform setups that were previously missing or only covered briefly.

🚀 Changes

• New File: Created docs/social_media_guide.md with detailed, step-by-step configuration instructions for:
  • WhatsApp (Docker bridge setup)
  • Feishu / Lark (Custom app & event subscription)
  • Telegram, Discord, QQ, DingTalk, LINE, and Slack.
• Updated README: Added a direct link to this guide under the "Chat Apps" section in the main README.md to help users find advanced configuration steps easily.

🎯 Value

This guide aims to reduce setup friction for users trying to connect PicoClaw to more complex platforms like WhatsApp and Feishu, ensuring they have a single source of truth for all channel configurations.

[nikolasdehor]

This PR does not contain what the description claims. The PR description says it adds a comprehensive Social Media Integration Guide (docs/social_media_guide.md) and updates the README with a link, but the actual diff only adds a single file called PicoClaw-guide containing:

git am < path/to/picoclaw-docs.patch

This is a git command, not documentation. The described files (docs/social_media_guide.md, README.md update) are not present in the diff at all.

It looks like the actual documentation content was prepared as a git patch file but never applied. The PR should contain the actual markdown documentation, not a shell command referencing a local patch file.

Please recreate this PR with the actual documentation content committed.

[firaseth]

Hi Sorry for this error , I will try to fix it  and you can check my repo under this name then you can fork it and to the original repo . Sent from my iPhoneOn 20 Feb 2026, at 3:26 PM, Nikolas Hor ***@***.***> wrote: @nikolasdehor requested changes on this pull request. This PR does not contain what the description claims. The PR description says it adds a comprehensive Social Media Integration Guide (docs/social_media_guide.md) and updates the README with a link, but the actual diff only adds a single file called PicoClaw-guide containing: git am < path/to/picoclaw-docs.patch This is a git command, not documentation. The described files (docs/social_media_guide.md, README.md update) are not present in the diff at all. It looks like the actual documentation content was prepared as a git patch file but never applied. The PR should contain the actual markdown documentation, not a shell command referencing a local patch file. Please recreate this PR with the actual documentation content committed. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[nikolasdehor]

The content is thorough and well-organized, covering all the major messaging platforms. However, there are issues that need to be fixed:

1. File naming and extension: The file is named 'PicoClaw-guide' with no extension. It should be 'PicoClaw-guide.md' since it contains Markdown content. Without the .md extension, GitHub will not render it properly.

2. File location: A guide this large (780 lines) should go in a docs/ directory rather than the repository root. The root is already getting cluttered with multiple README translations.

3. Potential security concern: The guide includes placeholder API keys and tokens that look realistic (e.g., 'YOUR_BOT_TOKEN', 'sk-xxx'). While these are obviously placeholders, some of the config examples show full JSON structures that could be copy-pasted by users who forget to replace all the placeholder values. Consider using more obviously fake values like 'REPLACE_ME_WITH_YOUR_TOKEN'.

4. No PR description or linked issue: The PR body is empty, making it hard to understand the motivation.

Please at minimum rename the file to PicoClaw-guide.md and consider moving it to docs/.

[firaseth]

Thanks Nicolas Already I did all necessary API changes to be secure and I forked your repo and I add my file in docs. Once again thanks for your a kind help and hope you with all your colleagues to support my GitHub account. Sent from my iPhoneOn 3 Mar 2026, at 7:02 AM, Nikolas Hor ***@***.***> wrote: @nikolasdehor requested changes on this pull request. The content is thorough and well-organized, covering all the major messaging platforms. However, there are issues that need to be fixed: File naming and extension: The file is named 'PicoClaw-guide' with no extension. It should be 'PicoClaw-guide.md' since it contains Markdown content. Without the .md extension, GitHub will not render it properly. File location: A guide this large (780 lines) should go in a docs/ directory rather than the repository root. The root is already getting cluttered with multiple README translations. Potential security concern: The guide includes placeholder API keys and tokens that look realistic (e.g., 'YOUR_BOT_TOKEN', 'sk-xxx'). While these are obviously placeholders, some of the config examples show full JSON structures that could be copy-pasted by users who forget to replace all the placeholder values. Consider using more obviously fake values like 'REPLACE_ME_WITH_YOUR_TOKEN'. No PR description or linked issue: The PR body is empty, making it hard to understand the motivation. Please at minimum rename the file to PicoClaw-guide.md and consider moving it to docs/. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>