feat(skills): add auto-update notification and skill versioning#1427
feat(skills): add auto-update notification and skill versioning#1427
Conversation
- Add wren-quickstart skill: end-to-end onboarding flow that orchestrates generate-mdl, wren-project, and wren-mcp-setup from zero to first query - Add wren-mcp-setup skill: Docker container setup + MCP client registration - Rename mdl-project → wren-project for consistency with skill naming convention - Update install.sh, README.md, and SKILLS.md to reflect new skills Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis PR renames the "mdl-project" skill to "wren-project" across documentation, configuration, and skill manifests, while introducing new "wren-mcp-setup" and "wren-quickstart" skills to streamline MCP server integration and onboarding workflows. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
skills/SKILLS.md (2)
170-186:⚠️ Potential issue | 🟡 MinorUpdate the example invocations to include the newly added skills.
The reference now documents
wren-quickstartandwren-mcp-setup, but this example still only shows the older subset. That makes the bottom-of-page usage snippet stale.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/SKILLS.md` around lines 170 - 186, The example invocation list under "Installing a skill" is stale; update the snippet that currently lists "/generate-mdl", "/wren-project", "/wren-sql" to also include the newly added skill commands "/wren-quickstart" and "/wren-mcp-setup" so the documented usage matches the skills referenced elsewhere; locate the invocation block in SKILLS.md and append or reorder entries to include "/wren-quickstart" and "/wren-mcp-setup" alongside the existing commands.
159-166:⚠️ Potential issue | 🟠 MajorSync this workflow summary with the new
wren-mcp-setupinstructions.This section still describes the old
docker compose/docker/.envflow, but the new skill now walks users through adocker runsetup. Anyone relying onSKILLS.mdalone will follow the wrong startup path.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/SKILLS.md` around lines 159 - 166, Update the "Workflow summary" to match the new wren-mcp-setup flow: replace the old steps about creating `docker/.env` and `docker compose up -d` with the `docker run` startup instructions used in `wren-mcp-setup` (include the required environment variable usage and the exact `docker run` behavior), ensure step 4 still mentions rewriting `localhost` → `host.docker.internal` in connection credentials, keep the step that adds the `wren` MCP server to Claude Code (port 9000 / streamable-http) and retain the final `health_check()` verification step so the summary mirrors the new `wren-mcp-setup` instructions exactly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/generate-mdl/SKILL.md`:
- Around line 23-25: The doc currently uses two payload names—connectionInfo and
conn_info—which will confuse agents; standardize on a single name (use
connectionInfo) across the entire document by replacing every occurrence of
conn_info with connectionInfo, including the "Connection info format" section,
any examples, example JSON/YAML payloads, and parameter references in the schema
filter sentence, and ensure all code/usage snippets (e.g., examples showing how
to pass connection info) match the connectionInfo shape exactly.
In `@skills/wren-mcp-setup/SKILL.md`:
- Around line 309-348: The MCP registration in "Step 8" is duplicated and breaks
flow because Steps 6/7 require MCP tools; either remove this Step 8 block or
move its instructions (the "wren" registration via `claude mcp add` and the
`~/.claude/settings.json` example and `claude mcp list` verification) up to Step
4 so registration occurs before Steps 6/7, and keep the existing note about
starting a new session; update any references in Steps 6/7 to assume the "wren"
MCP is already registered.
In `@skills/wren-quickstart/SKILL.md`:
- Around line 137-149: The doc erroneously instructs calling health_check()
immediately after MCP registration even though the MCP tools load only on
session start; update the text to require the user to start a new session after
registering the MCP server and then run health_check() in that new session.
Modify the paragraph that currently says "Use health_check() to verify Wren
Engine is reachable" to first instruct "Start a new session so the Wren MCP
tools are fully loaded, then run health_check()" and keep the remaining steps
(tell the user setup is complete and that in the new session they can start
querying). Ensure you reference health_check(), the MCP server registration
step, and "start a new session" in the revised wording.
- Line 30: Update the parenthetical "all Wren skills" list in SKILL.md to
include `wren-sql` alongside `generate-mdl`, `wren-project`, `wren-mcp-setup`,
and `wren-quickstart`; locate the sentence that reads "This installs all Wren
skills (`generate-mdl`, `wren-project`, `wren-mcp-setup`, `wren-quickstart`)
into `~/.claude/skills/`." and add `wren-sql` to that parenthetical list so it
accurately matches what `bash skills/install.sh` installs.
---
Outside diff comments:
In `@skills/SKILLS.md`:
- Around line 170-186: The example invocation list under "Installing a skill" is
stale; update the snippet that currently lists "/generate-mdl", "/wren-project",
"/wren-sql" to also include the newly added skill commands "/wren-quickstart"
and "/wren-mcp-setup" so the documented usage matches the skills referenced
elsewhere; locate the invocation block in SKILLS.md and append or reorder
entries to include "/wren-quickstart" and "/wren-mcp-setup" alongside the
existing commands.
- Around line 159-166: Update the "Workflow summary" to match the new
wren-mcp-setup flow: replace the old steps about creating `docker/.env` and
`docker compose up -d` with the `docker run` startup instructions used in
`wren-mcp-setup` (include the required environment variable usage and the exact
`docker run` behavior), ensure step 4 still mentions rewriting `localhost` →
`host.docker.internal` in connection credentials, keep the step that adds the
`wren` MCP server to Claude Code (port 9000 / streamable-http) and retain the
final `health_check()` verification step so the summary mirrors the new
`wren-mcp-setup` instructions exactly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 6df4c55d-4b1f-4781-95dd-3b391f346d3d
📒 Files selected for processing (8)
mcp-server/README.mdskills/README.mdskills/SKILLS.mdskills/generate-mdl/SKILL.mdskills/install.shskills/wren-mcp-setup/SKILL.mdskills/wren-project/SKILL.mdskills/wren-quickstart/SKILL.md
Each SKILL.md now checks versions.json on invocation and notifies the user if a newer version is available, so updates are surfaced at the natural moment of use rather than requiring manual checking. - Add skills/versions.json as the lightweight version registry - Add ## Version check section to all 5 SKILL.md files - Add update reminder to install.sh post-install output - Document update and release workflow in skills/README.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Remove duplicate Step 8 from wren-mcp-setup (MCP registration already covered in Steps 4/5; placing it after Steps 6/7 that require MCP tools was logically incorrect) - Fix wren-quickstart Phase 5 to require a new session before running health_check() — MCP tools only load on session start - Add missing wren-sql to installed skills list in wren-quickstart - Add /wren-mcp-setup and /wren-quickstart to SKILLS.md invocation examples - Update stale docker-compose workflow summary in SKILLS.md to reflect the current docker run approach Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Consistent naming across the entire document to avoid confusing agents. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
mdl-projectskill towren-projectfor consistent naming with thewren-prefix conventionwren-mcp-setupskill for Docker-based MCP server setupwren-quickstartend-to-end onboarding skillversions.jsonon invocation and notifies the user if a newer version is available, surfacing updates at the natural moment of useskills/versions.jsonas the canonical version registryskills/README.mdHow the update mechanism works
When a user invokes a skill (e.g.
/generate-mdl), the AI agent silently fetchesversions.jsonfrom the main branch and compares the remote version against the locally installed version. If the remote is newer, the agent notifies the user with a one-liner update command before continuing:Releasing a new version requires bumping
versionin the skill'sSKILL.mdfrontmatter and updatingskills/versions.jsonto match.Test plan
bash skills/install.sh --force wren-projectinstalls correctlybash skills/install.sh --force wren-mcp-setupinstalls correctlybash skills/install.sh(all skills) completes without errors and shows update hint/generate-mdl(or any skill) in Claude Code triggers a version checkversions.jsoncauses the skill to notify the user on next invocation🤖 Generated with Claude Code