agentleFS
jamie8johnsonjamie8johnson/cqs/.claude/skills/reindex/SKILL.md

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

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
  1. Very specific:

    Before stats: Run cqs stats and capture output (chunk count, note count, HNSW status)

    line 14
  2. Very specific:

    Default: cqs index (incremental — only re-embeds changed files)

    line 17
  3. Very specific:

    After stats: Run cqs stats again

    line 20
  4. Distinctive:

    Call graph: call count change

    line 26
  5. Distinctive:

    Verify: Run a quick search to confirm index is working:

    line 28
  6. Distinctive:

    If no results, something is wrong — investigate

    line 30
  7. Distinctive:

    After significant code changes

    line 34
  8. Very specific:

    After editing docs/notes.toml manually (if cqs watch isn't running)

    line 35
  9. Distinctive:

    After switching branches with different file sets

    line 36
  10. Distinctive:

    When search results seem stale or wrong

    line 37

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reindex

Rebuild the cqs search index and compare stats.

Process

  1. Before stats: Run cqs stats and capture output (chunk count, note count, HNSW status)
  2. Reindex:
    • Default: cqs index (incremental — only re-embeds changed files)
    • With --force argument: cqs index --force (full rebuild). Stop the daemon first (systemctl --user stop cqs-watch) — cqs itself warns to do this — and restart it after.
  3. After stats: Run cqs stats again
  4. Compare: Show before/after diff:
    • Chunks: added, removed, unchanged
    • Notes: count change
    • HNSW vectors: count change
    • Call graph: call count change
  5. 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.toml manually (if cqs watch isn't running)
  • After switching branches with different file sets
  • When search results seem stale or wrong

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.