v0.1.13: Per-project MCP servers and auto-init detection#67
Merged
Conversation
Move MCP server configuration from global install to per-project init: - Add project-level MCP layer (.claude/mcp.json) as highest precedence in CompileContext.mcp_layers - Create /init skill with tech stack detection and MCP server selection - Auto-detect uninitialized projects in `shipkit run` and inject init hint so the agent offers to run /init on first launch - Remove MCP selection from install skill (Phase 3.2) - Bump version to 0.1.13
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
1 participant
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
.claude/mcp.json) as highest precedence in the MCP layer system/initskill that detects tech stack and walks users through selecting MCP servers per-projectshipkit run— injects a prompt hint so the agent offers/initon first launchTest plan