Remove jetpack/subscriptions newsletter signup recommendation - #3619
Merged
Conversation
The jetpack/subscriptions block requires a Jetpack/WordPress.com connection to actually create subscribers, which Studio sites do not have by default. Recommending it caused the agent to generate markup that renders an empty form on the frontend. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
📊 Performance Test ResultsComparing ebe4158 vs trunk app-size
site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
lezama
approved these changes
May 26, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
How AI was used in this PR
Claude Code edited the agent's
plugin-recommendationsskill and the related routing references to drop thejetpack/subscriptionsblock recommendation. I reviewed the diff and confirmed the remaining Jetpack Forms section is unchanged.Proposed Changes
## Newsletter Signupsection from apps/cli/ai/skills/plugin-recommendations/SKILL.md, along with the cross-reference paragraph in the## Jetpack Formssection and the "newsletter signup" mention in the skill intro/precedence note.jetpack/subscriptionsfrom thecore/htmlform-markup policy message in apps/cli/ai/block-content-policy.ts.Why
jetpack/subscriptionsrequires a Jetpack / WordPress.com connection to actually create subscribers. Local Studio sites don't have that connection by default, so when the agent generated newsletter signup markup, the block rendered as an empty form on the frontend. Removing the recommendation prevents that failure mode until we have a story for the connection step. Jetpack Forms (contact form) does not have the same requirement and stays in the skill.Testing Instructions
npm test -- apps/cli/ai/tests/block-content-policy.test.ts apps/cli/ai/tests/system-prompt.test.ts— 11/11 pass.jetpack/subscriptions. The Jetpack Forms / contact-form path should still work for contact forms.Pre-merge Checklist