Skip to content
Back to skills

Migrate

ASecurity

Handle cqs schema version upgrades — check version, attempt migration, rebuild if needed.

  • 18 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsbashgitdatabase

Security analysis

A93/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned November 7, 2026

npx -y skills add jamie8johnson/cqs --skill migrate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Migrate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Migrate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jamie8johnson-migrate/badge)](https://www.skillsdirectory.com/skills/jamie8johnson-migrate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: migrate
description: Handle cqs schema version upgrades — check version, attempt migration, rebuild if needed.
disable-model-invocation: false
argument-hint: ""
---

# Migrate

Handle schema version mismatches when upgrading cqs.

## Process

### 1. Check current schema version

```bash
cqs stats 2>&1
```

If it works normally, no migration needed. If you see a schema error, continue.

### 2. Identify the mismatch

Errors tell you the versions:
- **SchemaMismatch(path, from, to)**: Index is at version `from`, cqs expects `to`. Auto-migration was attempted but no migration path exists.
- **SchemaNewerThanCq(version)**: Index was created by a newer cqs version. Update your binary.

### 3. Attempt migration

cqs attempts auto-migration when it opens the database. If you're seeing SchemaMismatch, it means no migration path exists for that version jump.

Check available migrations:
```bash
grep -n "migrate_v" src/store/migrations.rs
```

### 4. Rebuild if no migration path

When auto-migration isn't available, the only option is a full rebuild:

```bash
# Back up the old index (just in case)
cp -r .cqs/ .cq.backup/

# Delete and rebuild
rm -rf .cqs/
cqs init
cqs index
```

This re-parses all source files and re-embeds them. Notes in `docs/notes.toml` are preserved (they live outside `.cqs/`).

### 5. Rebuild references too

References have their own databases at the same schema version:

```bash
cqs ref list
```

For each reference:
```bash
cqs ref update <name>
```

If that fails with schema errors, remove and re-add:
```bash
cqs ref remove <name>
cqs ref add <name> <source_path> --weight <weight>
```

### 6. Verify

```bash
cqs stats
```

Should show the current schema version and correct chunk counts.

### 7. Clean up

```bash
rm -rf .cq.backup/
```

## Notes

- `.cqs/` is gitignored — rebuilding only costs time, not data. But it now holds named slots (`.cqs/slots/<name>/index.db`) and the embeddings cache (`.cqs/embeddings_cache.db`) — `rm -rf .cqs/` nukes ALL slots and the cache. Prefer removing just the broken slot dir if only one slot is affected.
- Notes (`docs/notes.toml`) are never lost — they're separate from the index
- Schema version is stored in `metadata` table: `SELECT value FROM metadata WHERE key = 'schema_version'`
- Current version: v28 (always confirm against `src/store/helpers/mod.rs:CURRENT_SCHEMA_VERSION`)
- Stop the daemon before destructive steps: `systemctl --user stop cqs-watch` (restart after)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.