bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README…
Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills/**/SKILL.md or guide/_shared file and BEFORE running content-evals — otherwise the eval silently
Claude Code
$ npx -y skills add hyhmrright/logic-lens --skill sync-skill-cache --agent claude-code
Codex
$ npx skills add hyhmrright/logic-lens --skill sync-skill-cache -a codex -y
Cursor
$ npx skills add hyhmrright/logic-lens --skill sync-skill-cache -a cursor -y
Gemini CLI
$ npx skills add hyhmrright/logic-lens --skill sync-skill-cache -a gemini-cli -y
GitHub Copilot
$ npx skills add hyhmrright/logic-lens --skill sync-skill-cache -a github-copilot -y
OpenCode
$ npx skills add hyhmrright/logic-lens --skill sync-skill-cache -a opencode -y
Windsurf
$ npx skills add hyhmrright/logic-lens --skill sync-skill-cache -a windsurf -y
name: sync-skill-cache
description: Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills/**/SKILL.md or guide/_shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is wasted. Also use to verify the cache is in sync ("is the cache fresh?", "did my edit take effect in evals?", "check skill cache drift").
disable-model-invocation: truecontent-evals invoke each skill through Claude Code's plugin mechanism, which loads from `~/.claude/plugins/cache/logic-lens-marketplace/logic-lens/<version>/skills/` — **not** the repo's `skills/`. Editing `skills/` changes nothing the eval sees until you copy it into the cache. This is the single most expensive footgun in the iteration loop: skip it and you grade the previous skill while believing you tested your change.
1. **Sync + verify** from the repo root:
bash .claude/skills/sync-skill-cache/scripts/sync-cache.sh
The script reads the active version from `package.json`, rsyncs `skills/` into the matching cache dir (`--delete`, so removed files are removed in the cache too), then diffs the two to confirm they are byte-identical. It prints `OK …` on success.
2. **If it prints `DRIFT` or a missing-cache error:** do not run evals. The two common causes:
this version) — reinstall/refresh the plugin, or check you didn't just bump the version without refreshing the cache.
3. **Verify-only mode** (no copy) to answer "is the cache fresh?":
bash .claude/skills/sync-skill-cache/scripts/sync-cache.sh --check
This skill is the mandatory gate between editing a skill and grading it. The `iterate-skill` orchestrator calls it automatically; run it by hand whenever you edit a skill outside that loop.
Logic-first bug investigation for coding assistants: establish behavioral contracts, follow real callers and dependencies, trace failure paths, and report reproducible violations with evidence.
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README…
Run the Logic-Lens skill-improvement loop end to end — baseline → diagnose failures → edit → sync cache → re-eval → verify net…
Scaffold a new logic-* skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is…
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change.…
Compare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side. Trigger when the user…
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.