Skip to content

Add @userid_checkbot — Telegram User/Chat/Channel ID lookup bot#218

Open
0xvibly wants to merge 2 commits into
ebertti:masterfrom
0xvibly:add-userid-checkbot
Open

Add @userid_checkbot — Telegram User/Chat/Channel ID lookup bot#218
0xvibly wants to merge 2 commits into
ebertti:masterfrom
0xvibly:add-userid-checkbot

Conversation

@0xvibly
Copy link
Copy Markdown

@0xvibly 0xvibly commented May 13, 2026

Adding @userid_checkbot to the Bots section.

Bot: @userid_checkbot
Website: telegramuserid.com

A utility bot that instantly finds your Telegram User ID, Chat ID, or Channel ID. No setup required — just start the bot and it returns your IDs.

Also available as a web tool at telegramuserid.com.

Copy link
Copy Markdown

@codesnifai codesnifai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 CodeSnif AI Review

This pull request adds the @userid_checkbot to the Bots section of the README, providing users with a utility bot for retrieving their Telegram User ID, Chat ID, or Channel ID. It includes a brief description and a link to the bot and its website.


Risk Level 🟢 LOW
Merge Advice merge now
Breaking Changes ✅ None detected

📋 Walkthrough

  • Added @userid_checkbot to the Bots section of the README.
  • Included links to the bot and its website.

🔍 Pre-merge Checks

  • ❌ The changes are minor and limited to documentation.
  • ❌ No functional code changes are introduced.

✨ Highlights

  • The addition enhances the documentation by providing useful resources for users.
  • The bot is straightforward and requires no setup, making it user-friendly.

🧪 Testing Notes

No testing required as this is a documentation change.

Powered by CodeSnif · AI-powered PR analysis

Copy link
Copy Markdown
Contributor

@devloai devloai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary:

  • Adds @userid_checkbot to the Bots section of the awesome list.
  • The bot provides instant Telegram User ID, Chat ID, and Channel ID lookup.
  • Also references telegramuserid.com as a companion web tool.
  • Single, focused contribution — no bulk submissions.

Review Summary:

The bot is a legitimate and useful Telegram utility with no existing duplicate in the list. The PR title is descriptive and the category placement is appropriate. However, the entry has three formatting violations relative to the repository's established conventions: a hyphen is used instead of the required em dash (), an unnecessary extra blank line was introduced before the entry (creating a double blank line), and there is no blank line separating the new entry from the ### Inline Bots section heading. These need to be corrected before merging.

Suggestions

  • Fix the three formatting issues flagged in the inline comment (em dash, blank lines) and I can apply the changes for you. Apply
  • Add a trailing blank line after the entry to properly separate it from the ### Inline Bots section. Apply

Comment thread README.md Outdated
* [MoniPayBot](https://t.me/monipaybot) – Gasless stablecoin payments, tipping, and gated access subscription management on Telegram. Send USDC, USDT, or USDT0 to any @username across Base, BSC, Celo, Ink, and Solana. Non-custodial.


* [@userid_checkbot](https://t.me/userid_checkbot) - Instantly find your Telegram User ID, Chat ID, or Channel ID. Also available at [telegramuserid.com](https://telegramuserid.com).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Three formatting issues with this entry:

  1. Wrong dash: Uses a hyphen (-) instead of the required em dash (). Every other entry in the list uses .
  2. Extra blank line: An unnecessary blank line was added at line 61 (the added + before this entry), resulting in two consecutive blank lines (lines 60–61) before the entry.
  3. Missing blank line after entry: There's no blank line between this entry and ### Inline Bots on line 63, breaking the section separation pattern used throughout the file.

Suggested fix for line 62 (also remove the extra blank line at 61):

Suggested change
* [@userid_checkbot](https://t.me/userid_checkbot) - Instantly find your Telegram User ID, Chat ID, or Channel ID. Also available at [telegramuserid.com](https://telegramuserid.com).
* [@userid_checkbot](https://t.me/userid_checkbot) Instantly find your Telegram User ID, Chat ID, or Channel ID. Also available at [telegramuserid.com](https://telegramuserid.com).
actions

Feedback: Rate this comment to help me improve future code reviews:

  • 👍 Good - Helpful and accurate
  • 👎 Poor - Wrong, unclear, or unhelpful
  • Skip if you don't have any strong opinions either way.

Copy link
Copy Markdown

@codesnifai codesnifai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 CodeSnif AI Review

This pull request adds the @userid_checkbot to the Bots section of the README file, providing users with a utility bot for retrieving their Telegram User ID, Chat ID, or Channel ID. The addition includes a link to the bot and its website for easy access.


Risk Level 🟢 LOW
Merge Advice merge now
Breaking Changes ✅ None detected

📋 Walkthrough

  • Added @userid_checkbot to the Bots section of the README.
  • Included links to the bot and its website.

🔍 Pre-merge Checks

  • ❌ The change is limited to documentation.
  • ❌ No functional code changes are introduced.

✨ Highlights

  • The addition enhances the documentation by providing useful resources for users.
  • The bot is straightforward and requires no setup, making it user-friendly.

🧪 Testing Notes

No specific testing is required, but a review of the README formatting and links is advisable.

Powered by CodeSnif · AI-powered PR analysis

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

Successfully merging this pull request may close these issues.

1 participant