reindex
Skill18 starsChanged 5 months agoMITView on GitHub
Rebuild the cqs index and show before/after stats comparison.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- replybr/plugadvpltheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- hydra-db/hydradb-claude-code★ 4same name
- replybr/plugadvpl★ 1same name
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
- migrateSkill
- prSkill
- recall-gateSkill
- releaseSkill
- troubleshootSkill
- update-tearsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Before stats: Run cqs stats and capture output (chunk count, note count, HNSW status)
- Very specific: line 17
Default: cqs index (incremental — only re-embeds changed files)
- Very specific: line 20
After stats: Run cqs stats again
- Distinctive: line 26
Call graph: call count change
- Distinctive: line 28
Verify: Run a quick search to confirm index is working:
- Distinctive: line 30
If no results, something is wrong — investigate
- Distinctive: line 34
After significant code changes
- Very specific: line 35
After editing docs/notes.toml manually (if cqs watch isn't running)
- Distinctive: line 36
After switching branches with different file sets
- Distinctive: line 37
When search results seem stale or wrong
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reindex
Rebuild the cqs search index and compare stats.
Process
- Before stats: Run
cqs statsand capture output (chunk count, note count, HNSW status) - Reindex:
- Default:
cqs index(incremental — only re-embeds changed files) - With
--forceargument:cqs index --force(full rebuild). Stop the daemon first (systemctl --user stop cqs-watch) — cqs itself warns to do this — and restart it after.
- Default:
- After stats: Run
cqs statsagain - Compare: Show before/after diff:
- Chunks: added, removed, unchanged
- Notes: count change
- HNSW vectors: count change
- Call graph: call count change
- Verify: Run a quick search to confirm index is working:
cqs "parse source file"— should return results- If no results, something is wrong — investigate
When to use
- After significant code changes
- After editing
docs/notes.tomlmanually (ifcqs watchisn't running) - After switching branches with different file sets
- When search results seem stale or wrong
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.

