migrate
Skill18 starsChanged 5 months agoMITView on GitHub
Handle cqs schema version upgrades — check version, attempt migration, rebuild if needed.
- Deletes or force-pushes
65 other projects use a version of this.
Adopted by
Most recently taken up by
- focusreactive/webflow-to-sanity-migrationtheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- tuist/agent-plugintheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use incident, sdd and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JkudjoSkillincident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record
Also in 4 projects that use this
liatrio-labsSkillsdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
Also in 4 projects that use this
BerryKuipersSkillscaffold
Detect project stack, apply architecture patterns, wire quality gates, and scaffold features. Use when bootstrapping a project, adding a vertical slice, wiring CI/CD, adding Docker compose, or setting up quality gates.
Also in 4 projects that use this
agenticnotetakingSkillupgrade
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Also in 3 projects that use this
genomewalkerSkillcheckpoint
Save a checkpoint of task status, decisions, active files, and next steps
Also in 5 projects that use this
JohnJBorenSkillci-cd
CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies
Also in 3 projects that use this
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 65
- garrytan/gbrain★ 33ksame name
- tuist/tuist★ 5.9ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- codewithmukesh/dotnet-claude-kit★ 808same name
- dsifry/metaswarm★ 432same name
- pipecat-ai/gradient-bang★ 420same name
- govctl-org/govctl★ 276same name
- AsiaOstrich/universal-dev-standards★ 84same name
55 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- archeoSkill
- auditSkill
- before-editSkill
- boundary-probeSkill
- check-my-workSkill
- cqs-batchSkill
- cqs-bootstrapSkill
- cqs-planSkill
- cqsSkill
- cqs-verifySkill
- docs-reviewSkill
- groom-notesSkill
- idleSkill
- investigateSkill
- landSkill
- prSkill
- recall-gateSkill
- reindexSkill
- releaseSkill
- troubleshootSkill
- update-tearsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
If it works normally, no migration needed.
- Distinctive: line 39
When auto-migration isn't available, the only option is a full rebuild:
- Distinctive: line 66
If that fails with schema errors, remove and re-add:
- Distinctive: line 78
Should show the current schema version and correct chunk counts.
- Very specific: line 92
Stop the daemon before destructive steps: systemctl --user stop cqs-watch (restart after)
“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Migrate
Handle schema version mismatches when upgrading cqs.
Process
1. Check current schema version
cqs stats 2>&1If 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 expectsto. 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:
grep -n "migrate_v" src/store/migrations.rs4. Rebuild if no migration path
When auto-migration isn't available, the only option is a full rebuild:
# Back up the old index (just in case)
cp -r .cqs/ .cq.backup/
# Delete and rebuild
rm -rf .cqs/
cqs init
cqs indexThis 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:
cqs ref listFor each reference:
cqs ref update <name>If that fails with schema errors, remove and re-add:
cqs ref remove <name>
cqs ref add <name> <source_path> --weight <weight>6. Verify
cqs statsShould show the current schema version and correct chunk counts.
7. Clean up
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
metadatatable: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)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

