docs: recommend MCP install over long-term CLI use - #3
Merged
Conversation
Point the getting-started skill and README at kody install plus host search/execute. Refresh the scoped ship-pr and orchestrate skills from the Kody registry. Co-authored-by: Kent C. Dodds <me+github@kentcdodds.com>
kody-bot
marked this pull request as ready for review
August 22, 2026 14:46
|
@cursor review |
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
2 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.
The getting-started skill and README treated the CLI (
kody login/kody search/kody execute) as the everyday interface.Change: recommend
kody installso the host talks to Kody over MCP. Keep CLI login/search/execute as bootstrap, scripts, or hosts that cannot run MCP.Also refresh the scoped
ship-prandorchestrateskills from the Kody registry (Bugbot-first reviewers, standing auto-ship policy,conductcallout) while keeping@kodycodes/cligates (npm run validate, publish via semantic-release).Local gate:
npm run validate. Docs/skill only — no protocol or login changes.