Prefer forking trusted community packages over creating from scratch - #804
Merged
Merged
Conversation
📝 WalkthroughWalkthroughThe change adds trusted community-package reuse guidance across documentation and agent instructions, and replaces featured onboarding listing links with interactive starter cards that install or fork packages and provide a setup prompt. ChangesCommunity package onboarding
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
kody-bot
marked this pull request as ready for review
July 20, 2026 17:46
Contributor
|
🔎 Preview deployed: https://kody-pr-804.kody-a99.workers.dev Worker: Mocks:
|
Prefer community_search/community_fork in onboarding prompts, MCP lifecycle instructions, and official guides. Add in-place Install on onboarding starter cards that becomes Copy prompt after success.
Local Playwright lacks Cloudflare credentials for repo-backed forks; fulfill install.json so the Install → Copy prompt UI path still runs.
Disable close-on-anchor-click so Install → Copy prompt can copy without the popover dismissing the interaction, and tighten the e2e assertion.
cursor
Bot
force-pushed
the
cursor/fork-first-onboarding-3a1c
branch
from
July 20, 2026 17:57
6633d42 to
2465302
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
packages/worker/src/app/onboarding-data.node.test.ts (1)
10-18: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winCover the new one-click-install wording.
The prompt now advertises one-click install on
/onboardingand listing details, but this test does not protect that new user-facing path. Add an assertion such asexpect(prompt).toContain('one-click install')so the guidance cannot regress unnoticed.Proposed test addition
expect(prompt).toContain('community_fork') + expect(prompt).toContain('one-click install') expect(prompt).toContain(🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/worker/src/app/onboarding-data.node.test.ts` around lines 10 - 18, Add an assertion to the existing onboarding prompt test around buildOnboardingSetupPrompt that verifies the prompt contains the exact “one-click install” wording, preserving the current assertions and test scope.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/worker/src/app/onboarding-data.node.test.ts`:
- Around line 10-18: Add an assertion to the existing onboarding prompt test
around buildOnboardingSetupPrompt that verifies the prompt contains the exact
“one-click install” wording, preserving the current assertions and test scope.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: fd75af7d-14aa-4576-a302-90d0f1acd0ce
📒 Files selected for processing (13)
docs/contributing/community-packages.mddocs/guides/README.mddocs/guides/integration-bootstrap.mddocs/guides/package-lifecycle.mddocs/use/community-packages.mddocs/use/first-steps.mde2e/community-featured.spec.tspackages/worker/client/routes/onboarding-starter-card.tsxpackages/worker/client/routes/onboarding.tsxpackages/worker/src/app/onboarding-data.node.test.tspackages/worker/src/app/onboarding-data.tspackages/worker/src/mcp/capabilities/coding/kody-official-guide.tspackages/worker/src/mcp/server-instructions.ts
2 of 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
3 participants
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.
Summary
Agents were steered to create packages after integration bootstrap, while community forking lived off the default path. This change steers agents to prefer trusted/close community packages first, and adds in-place one-click install on onboarding starter cards.
Agent steering
package_lifecycle/integration_bootstrapguides now say: after smoke test,community_search(prefer trusted), fork/adapt when close, create only when nothing suitable existsOnboarding UI
remix/ui/popoveras a hover/focus tooltip (Remix has no dedicated Tooltip)POST /community/:listingId/install.json(featured listings are trusted)Tests
featured_atmarks)System recap — composes existing primitives (low risk)
Mode: recap · Base:
main@a55b430b· Head:6633d42eClassification: composes — reuses community install, featured listings, MCP instructions, and official guides; no new primitives.
Primitives touched
mcp-servercapability-registryapp-uiapp-sessionsSystem map
Agents and onboarding both prefer trusted community packages before creating new ones; install stays on the existing community install API.
Legend: green = composes (wiring only) · amber = extended by this PR · red = new primitive · gray = context (unchanged, included only when an edge crosses it).
Change flow
flowchart TD need[Need durable package] searchOwn[search own capabilities/packages] community[community_search prefer trusted] close{Close enough?} fork[Fork or one-click install then adapt] create[Create new package] need --> searchOwn --> community --> close close -->|yes| fork close -->|no| createPlan vs actual
remix/ui/popoverSummary by CodeRabbit
New Features
Documentation