Skip to content

Rename wpcom:list-site-plugins to jetpack:list-site-plugins#131

Merged
Ninodevo merged 1 commit into
trunkfrom
rename/jetpack-list-site-plugins
Jun 1, 2026
Merged

Rename wpcom:list-site-plugins to jetpack:list-site-plugins#131
Ninodevo merged 1 commit into
trunkfrom
rename/jetpack-list-site-plugins

Conversation

@Ninodevo

@Ninodevo Ninodevo commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Rename the wpcom:list-site-plugins CLI command to jetpack:list-site-plugins. The wpcom prefix was misleading — the command hits the Jetpack plugins endpoint and works for both WPCOM- and Jetpack-connected sites.
  • Rename the command class/file WPCOM_Site_Plugins_ListJetpack_Site_Plugins_List and update its description/help text to mention both services.
  • Rename the matching MCP tool wpcom_list_site_pluginsjetpack_list_site_plugins and move it to the Jetpack row of the README tools table.
  • Refs T51ENG-1819.

Notes

  • Breaking change: no backward-compatible alias was added. Scripts/aliases using wpcom:list-site-plugins, and MCP clients referencing wpcom_list_site_plugins, must switch to the jetpack: / jetpack_ names.
  • The renamed MCP method still physically sits in the // region WPCOM TOOLS block (matching existing precedent — jetpack_export_site_plugins lives in the legacy region). Left in place to keep the diff minimal; can relocate to the Jetpack region on request.
  • The GitHub Wiki command reference still needs its page renamed to match (out of repo scope).

Test plan

  • team51 list shows jetpack:list-site-plugins and no longer lists wpcom:list-site-plugins.
  • team51 jetpack:list-site-plugins <site> prints the plugins table for both a WPCOM- and a Jetpack-connected site.
  • team51 --mcp exposes jetpack_list_site_plugins and not wpcom_list_site_plugins.
  • composer run lint:php passes for the changed files.

Summary by CodeRabbit

Release Notes

  • New Features

    • Site plugin listing tool now available for Jetpack-connected sites in addition to WPCOM sites
  • Documentation

    • Updated documentation to reflect expanded availability of the site plugins listing tool

The wpcom prefix was misleading: the command queries the Jetpack
plugins endpoint and works for both WPCOM- and Jetpack-connected
sites. Rename the command and its class, rename the matching MCP
tool, and move it to the Jetpack row of the README tools table.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 1, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 348b2f54-342a-40f2-ac7c-0180b824a0a9

📥 Commits

Reviewing files that changed from the base of the PR and between 2dd426c and 1520991.

📒 Files selected for processing (3)
  • README.md
  • commands/Jetpack_Site_Plugins_List.php
  • mcp/Team51McpTools.php

Walkthrough

This PR renames and retargets the site plugins listing feature from WPCOM-specific to Jetpack/combined scope. The MCP tool method was renamed from wpcom_list_site_plugins to jetpack_list_site_plugins, with the corresponding Symfony console command class and command name changed from WPCOM-specific to Jetpack-specific. The command help text was updated to reference "WPCOM or Jetpack-connected" sites. The README "Available Tools" table was updated to reflect the new tool availability under Jetpack instead of WPCOM. Core implementation logic and functionality remain unchanged.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the primary change: renaming a CLI command from wpcom to jetpack for site plugin listing.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch

Comment @coderabbitai help to get the list of available commands and usage tips.

@Ninodevo Ninodevo merged commit 8933739 into trunk Jun 1, 2026
7 of 10 checks passed
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