Skip to content

v1.4.2 — the describe command was arguing from a reversed result

Choose a tag to compare

@skymanbp skymanbp released this 26 Aug 01:38
· 12 commits to master since this release

/rag-your-code:describe made its case with "losing 31.4% vs 34.3% on an undescribed repository". That figure came from the subject retired in 1.4.0, and it reversed when the same question was asked of a second repository: a cold index beats a Grep loop on Flask, 37.1% to 22.9%. The command now says which half depends on the repository — how much prose it already carries — and keeps the half that does not: 22.9% against 58.6% once descriptions exist.

That surface was swept for fingerprints and unit counts in both 1.3.0 and 1.4.0 and passed each time, because neither sweep looked for bare percentages. The sweep was the thing that was wrong.

docs/FLOW.md draws the whole thing in four diagrams: the loop a user lives in, indexing, the answering path with both evidence bars and all four refusal reasons, and the three surfaces — four commands, one skill, and the nine-action JSON-lines protocol.

The README now says how to update the plugin, not only how to install it. claude plugin update rag-your-code is refused with Plugin "rag-your-code" not found, which reads like the plugin is gone rather than like the argument is short: it wants the full name@marketplace id, and the marketplace cache has to be refreshed first.

356 tests, unchanged — no .py file was touched, so every corpus fingerprint published in 1.4.1 still holds.