You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/AUTO_UPDATE.md
+30-8Lines changed: 30 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ The QSV MCP Server includes a comprehensive auto-update system that keeps your s
14
14
2.**Skill Definitions Updates**
15
15
- Auto-detected when qsv version changes
16
16
- Can be auto-regenerated (if configured)
17
-
- Manual regeneration: `cargo run --bin qsv-skill-gen --features all_features`
17
+
- Manual regeneration: `qsv --update-mcp-skills`
18
18
19
19
3.**MCP Server Code Updates**
20
20
- Checked against GitHub releases
@@ -135,13 +135,8 @@ jobs:
135
135
unzip qsv-linux-x86_64.zip
136
136
sudo mv qsv /usr/local/bin/
137
137
138
-
- name: Install Rust
139
-
uses: actions-rs/toolchain@v1
140
-
with:
141
-
toolchain: stable
142
-
143
138
- name: Regenerate skills
144
-
run: cargo run --bin qsv-skill-gen --features all_features
139
+
run: qsv --update-mcp-skills
145
140
146
141
- name: Build MCP server
147
142
run: |
@@ -229,11 +224,34 @@ This file is automatically managed and helps track update history.
229
224
230
225
**Solution**:
231
226
- Verify qsv binary location: `which qsv`
232
-
- Test manual regeneration: `qsv --update-mcp-skills`
227
+
- Ensure you're in the qsv repository: `pwd` (should show path ending in `/qsv`)
228
+
- Test manual regeneration: `cd /path/to/qsv && qsv --update-mcp-skills`
233
229
- Check if binary has mcp feature: `qsv --version` (shows installed features)
234
230
- Check MCP server logs: `~/Library/Logs/Claude/mcp*.log`
235
231
- If flag not available, rebuild qsv: `cargo build --release --features all_features`
236
232
233
+
### "Could not find qsv repository root" error
234
+
235
+
**Problem**: Running `qsv --update-mcp-skills` fails with "Could not find qsv repository root"
236
+
237
+
**Cause**: The command must be run from within the qsv repository directory structure (where `Cargo.toml` and `src/cmd` exist). This is because the skill generation writes to `.claude/skills/qsv/` relative to the repository root.
238
+
239
+
**Solution**:
240
+
1.**If you installed qsv via package manager** (Homebrew, cargo install, etc.):
241
+
- Clone the qsv repository: `git clone https://github.com/dathere/qsv.git`
242
+
- Navigate into it: `cd qsv`
243
+
- Run: `qsv --update-mcp-skills`
244
+
245
+
2.**If you built qsv from source**:
246
+
- Navigate to your qsv repository directory: `cd /path/to/qsv`
247
+
- Verify you're in the right place: `ls Cargo.toml src/cmd` (both should exist)
248
+
- Run: `qsv --update-mcp-skills`
249
+
250
+
3.**For auto-regeneration**:
251
+
- The MCP server must have access to the repository directory
252
+
- Auto-regeneration will fail if the qsv binary can't find the repository
253
+
- Consider using manual regeneration workflow if binary is installed system-wide
254
+
237
255
### Version check fails
238
256
239
257
**Problem**: Update checker reports errors
@@ -271,6 +289,10 @@ The update check runs asynchronously and doesn't block MCP server startup.
271
289
-**qsv binary** with "mcp" feature enabled
272
290
- Included in prebuilt binaries from GitHub releases
273
291
- When building from source: Use `cargo build --release --features all_features`
292
+
-**qsv repository** cloned locally
293
+
- The `--update-mcp-skills` command must be run from within the repository
294
+
- Outputs to `.claude/skills/qsv/` relative to repository root
0 commit comments