Skip to content

Add whatsapp-claude-plugin to Plugins & Extensions#35

Open
Rich627 wants to merge 1 commit intojmanhype:mainfrom
Rich627:add-whatsapp-claude-plugin
Open

Add whatsapp-claude-plugin to Plugins & Extensions#35
Rich627 wants to merge 1 commit intojmanhype:mainfrom
Rich627:add-whatsapp-claude-plugin

Conversation

@Rich627
Copy link
Copy Markdown

@Rich627 Rich627 commented Apr 13, 2026

Summary

  • Adds whatsapp-claude-plugin to the Plugins & Extensions table.
  • Bumps the "Plugins listed" count from 4 to 5.

Plugin: WhatsApp channel plugin for Claude Code — officially published on the Anthropic Plugin Marketplace. Connects as a linked device via Baileys v7 with bidirectional messaging, full media support, voice transcription, permission relay, and access control.

Author: Richie Liu (Rich627)

Checklist

  • Searched for duplicates
  • Individual PR for a single suggestion
  • Follows existing table format
  • Description is short, descriptive, and ends with a period
  • Spelling and grammar checked

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Add whatsapp-claude-plugin to Plugins & Extensions

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Adds whatsapp-claude-plugin to Plugins & Extensions table
• Updates plugin count from 4 to 5
• Plugin enables WhatsApp integration with Claude via Baileys
Diagram
flowchart LR
  A["Plugins & Extensions Table"] -- "add new entry" --> B["whatsapp-claude-plugin"]
  C["Plugin Count"] -- "increment" --> D["5 plugins"]
Loading

Grey Divider

File Changes

1. README.md ✨ Enhancement +1351/-68

Add WhatsApp Claude plugin to table

• Adds whatsapp-claude-plugin entry to Plugins & Extensions table
• Updates plugin count from 4 to 5
• Includes plugin description with Baileys v7 integration details
• Lists author as Richie Liu (Rich627)

README.md


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review bot commented Apr 13, 2026

Code Review by Qodo

🐞 Bugs (2)   📘 Rule violations (1)   📎 Requirement gaps (0)   🖥 UI issues (0)   🎨 UX Issues (0)
🐞\ ≡ Correctness (1) ⛨ Security (1)
📘\ ⚙ Maintainability (1)

Grey Divider


Action required

1. README plugin list format changed 📘
Description
The updated README.md uses large multi-column tables and descriptions that do not match the
repository’s documented listing format and punctuation conventions. This deviates from established
project patterns and makes the list harder to maintain consistently across contributions.
Code

README.md[R110-118]

+## Automation DevOps
+
+| Plugin | Marketplace | Description | Author | Version |
+|--------|-------------|-------------|--------|---------|
+| [deployment-engineer](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/deployment-engineer) | awesome-claude-code-plugins | Use this agent when setting up CI/CD pipelines, configuring Docker containers, deploying applications to cloud platforms, setting up Kubernetes clu... | Jure Šunić | 1.0.0 |
+| [devops-automator](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/devops-automator) | awesome-claude-code-plugins | Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment process... | Michael Galpert | 1.0.0 |
+| [infrastructure-maintainer](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/infrastructure-maintainer) | awesome-claude-code-plugins | Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels a... | Michael Galpert | 1.0.0 |
+| [monitoring-observability-specialist](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/monitoring-observability-specialist) | awesome-claude-code-plugins | Use this agent when you need to implement comprehensive monitoring, observability, and alerting systems for enterprise B2B applications. This agent... | Alysson Franklin | 1.0.0 |
+| [n8n-workflow-builder](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/n8n-workflow-builder) | awesome-claude-code-plugins | Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows usi... | Jure Šunić | 1.0.0 |
Evidence
The repository’s contribution guidelines define the expected entry pattern (`[Title](link) -
Description.`) and require descriptions to end with a period, but the newly added README sections
use a different table-based structure and contain entries without period-terminated descriptions
(e.g., Perform a comprehensive code review of recent changes).

CLAUDE.md
contributing.md[5-10]
README.md[110-118]
README.md[135-140]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`README.md` content does not follow the repository’s established listing style/patterns (as documented in `contributing.md`), including the required entry format and period-terminated descriptions.

## Issue Context
The repo’s contribution guidelines specify how plugin entries should be formatted, which helps keep the list consistent and maintainable.

## Fix Focus Areas
- contributing.md[5-10]
- README.md[110-118]
- README.md[135-140]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Unsafe curl|bash install 🐞
Description
README instructs users to execute a remote script via curl ... | bash, which allows arbitrary code
execution if the fetched content is compromised. Additionally, in typical shells the pipeline exit
status is from bash, so a failed curl can still look like a successful install (empty stdin).
Code

README.md[11]

+1. Install CAM: `curl -fsSL https://raw.githubusercontent.com/Chat2AnyLLM/code-assistant-manager/main/install.sh | bash`
Evidence
The installation section includes a one-liner that downloads a script from GitHub and pipes it
directly into bash, which executes the content without user inspection/verification.

README.md[9-12]
README.md[11-12]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README currently recommends installing by piping a downloaded script directly into `bash` ("curl | bash"). This is a well-known security footgun because it executes unverified remote content.

## Issue Context
This is user-facing documentation; readers will copy/paste these commands.

## Fix Focus Areas
- README.md[9-23]

## Suggested change
- Replace the one-liner with safer steps, e.g.:
 1) download to a file
 2) instruct the user to inspect it
 3) optionally verify checksum/signature
 4) then execute it explicitly (e.g. `bash install.sh`).
- If you keep a one-liner, at minimum provide an alternative “inspect first” flow and avoid implying this is the recommended secure approach.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

3. Broken TOC anchor links 🐞
Description
The Table of Contents links multiple entries to the same anchor (e.g., both “Data Analytics” and
“data-analytics” use #data-analytics, and both “Documentation” and “documentation” use
#documentation). Because the README contains both headings, GitHub will assign the later duplicate
heading a suffixed id (e.g., #data-analytics-1), so the later TOC entries will jump to the wrong
section.
Code

README.md[R25-78]

+## Table of Contents
+
+- [Automation DevOps](#automation-devops)
+- [Business Sales](#business-sales)
+- [Code Quality Testing](#code-quality-testing)
+- [Data Analytics](#data-analytics)
+- [Design UX](#design-ux)
+- [Development Engineering](#development-engineering)
+- [Documentation](#documentation)
+- [Git Workflow](#git-workflow)
+- [Marketing Growth](#marketing-growth)
+- [Official Claude Code Plugins](#official-claude-code-plugins)
+- [Project & Product Management](#project--product-management)
+- [Security, Compliance, & Legal](#security-compliance--legal)
+- [Uncategorized](#uncategorized)
+- [Workflow Orchestration](#workflow-orchestration)
+- [abap](#abap)
+- [accessibility](#accessibility)
+- [agents](#agents)
+- [ai](#ai)
+- [ai-agency](#ai-agency)
+- [ai-ml](#ai-ml)
+- [api](#api)
+- [api-development](#api-development)
+- [assets](#assets)
+- [automation](#automation)
+- [blockchain](#blockchain)
+- [btp](#btp)
+- [business](#business)
+- [business-marketing](#business-marketing)
+- [business-tools](#business-tools)
+- [cap](#cap)
+- [code-quality](#code-quality)
+- [code-review](#code-review)
+- [communication](#communication)
+- [communication-writing](#communication-writing)
+- [community](#community)
+- [content](#content)
+- [creative-media](#creative-media)
+- [crypto](#crypto)
+- [customization](#customization)
+- [data](#data)
+- [data-analytics](#data-analytics)
+- [database](#database)
+- [debugging](#debugging)
+- [deployment](#deployment)
+- [design](#design)
+- [dev-tools](#dev-tools)
+- [developer-tools](#developer-tools)
+- [development](#development)
+- [devops](#devops)
+- [document-conversion](#document-conversion)
+- [documentation](#documentation)
+- [example](#example)
Evidence
The TOC contains duplicate links for #data-analytics and #documentation, while the document
defines both the Title Case and lowercase/hyphenated headings later; these headings normalize to the
same slug, so the second occurrence gets a suffixed anchor and the TOC entry becomes incorrect.

README.md[25-78]
README.md[154-156]
README.md[730-733]
README.md[197-200]
README.md[946-949]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README Table of Contents contains multiple entries that link to identical anchors (e.g. `#data-analytics`, `#documentation`) even though the document has multiple headings that slugify to the same ids. On GitHub, later duplicate headings receive suffixed anchors (like `-1`), so these TOC entries will not navigate to the intended later sections.

## Issue Context
This README is large; TOC navigation needs to be reliable.

## Fix Focus Areas
- README.md[25-78]
- README.md[154-176]
- README.md[730-739]
- README.md[197-210]
- README.md[946-957]

## Suggested change
Pick one approach:
- Update the TOC links for the later duplicates to the expected suffixed anchors (e.g., `#data-analytics-1`, `#documentation-1`).
- Or rename one of each duplicated headings so they don’t collide when slugified (preferred long-term).
- Or remove redundant TOC entries if they are not needed.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Comment thread README.md
Comment on lines +110 to +118
## Automation DevOps

| Plugin | Marketplace | Description | Author | Version |
|--------|-------------|-------------|--------|---------|
| [deployment-engineer](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/deployment-engineer) | awesome-claude-code-plugins | Use this agent when setting up CI/CD pipelines, configuring Docker containers, deploying applications to cloud platforms, setting up Kubernetes clu... | Jure Šunić | 1.0.0 |
| [devops-automator](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/devops-automator) | awesome-claude-code-plugins | Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment process... | Michael Galpert | 1.0.0 |
| [infrastructure-maintainer](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/infrastructure-maintainer) | awesome-claude-code-plugins | Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels a... | Michael Galpert | 1.0.0 |
| [monitoring-observability-specialist](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/monitoring-observability-specialist) | awesome-claude-code-plugins | Use this agent when you need to implement comprehensive monitoring, observability, and alerting systems for enterprise B2B applications. This agent... | Alysson Franklin | 1.0.0 |
| [n8n-workflow-builder](https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/n8n-workflow-builder) | awesome-claude-code-plugins | Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows usi... | Jure Šunić | 1.0.0 |
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Action required

1. Readme plugin list format changed 📘 Rule violation ⚙ Maintainability

The updated README.md uses large multi-column tables and descriptions that do not match the
repository’s documented listing format and punctuation conventions. This deviates from established
project patterns and makes the list harder to maintain consistently across contributions.
Agent Prompt
## Issue description
`README.md` content does not follow the repository’s established listing style/patterns (as documented in `contributing.md`), including the required entry format and period-terminated descriptions.

## Issue Context
The repo’s contribution guidelines specify how plugin entries should be formatted, which helps keep the list consistent and maintainable.

## Fix Focus Areas
- contributing.md[5-10]
- README.md[110-118]
- README.md[135-140]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Comment thread README.md
- Plugin compatibility can break across Claude Code versions.
- Not all MCP servers have been tested against the latest release.
- Community editor integrations vary in maturity and maintenance cadence.
1. Install CAM: `curl -fsSL https://raw.githubusercontent.com/Chat2AnyLLM/code-assistant-manager/main/install.sh | bash`
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Action required

2. Unsafe curl|bash install 🐞 Bug ⛨ Security

README instructs users to execute a remote script via curl ... | bash, which allows arbitrary code
execution if the fetched content is compromised. Additionally, in typical shells the pipeline exit
status is from bash, so a failed curl can still look like a successful install (empty stdin).
Agent Prompt
## Issue description
The README currently recommends installing by piping a downloaded script directly into `bash` ("curl | bash"). This is a well-known security footgun because it executes unverified remote content.

## Issue Context
This is user-facing documentation; readers will copy/paste these commands.

## Fix Focus Areas
- README.md[9-23]

## Suggested change
- Replace the one-liner with safer steps, e.g.:
  1) download to a file
  2) instruct the user to inspect it
  3) optionally verify checksum/signature
  4) then execute it explicitly (e.g. `bash install.sh`).
- If you keep a one-liner, at minimum provide an alternative “inspect first” flow and avoid implying this is the recommended secure approach.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

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