/new-skill
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 missed. Use when adding a seventh (or later) skill to Logic-Lens.
$ npx -y skills add hyhmrright/logic-lens --skill new-skill --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/new-skill
Context preview
The summary Claude sees to decide when to auto-load this skill.
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 missed. Use when adding a seventh (or later) skill to Logic-Lens.
SKILL.md
new-skill.SKILL.mdname: new-skill
description: 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 missed. Use when adding a seventh (or later) skill to Logic-Lens.
disable-model-invocation: true
new-skill
CLAUDE.md → "Adding a New Skill" is the authoritative checklist. This skill exists to make sure *every* step actually runs — the session-start loop and the eval cases are the ones most often forgotten.
**Read CLAUDE.md's "Adding a New Skill" section now**, then execute its steps for `logic-<NAME>` (ask the user for `<NAME>` if not in `$ARGUMENTS`):
1. **`skills/logic-<NAME>/SKILL.md`** — copy the frontmatter shape from `skills/logic-review/SKILL.md` (`name` + `description`). The `description` MUST include a "Do NOT trigger for:" clause and a "SCOPE … RULE" line distinguishing it from the other skills. Process section = 5–7 numbered items, each citing a guide step. Follow lazy-loading per `skills/_shared/common.md` §13. 2. **`skills/logic-<NAME>/logic-<NAME>-guide.md`** — numbered steps (Step 1, 2, …), each explaining the *why*, concrete examples over abstractions. 3. **`commands/logic-<NAME>.md`** — mirror `commands/logic-review.md`:
---
description: <one line>
allowed-tools: Skill
---
Use the Skill tool to invoke `logic-lens:logic-<NAME>`, then follow its instructions exactly. $ARGUMENTS
4. **`hooks/session-start`** (CLAUDE.md step 6 — easy to miss) — add `logic-<NAME>` to BOTH the `for skill in …` loop and the printed skill list:
grep -n "for skill in" hooks/session-start
5. **Eval cases** (CLAUDE.md step 7 — easy to miss) — add 3–5 content cases to `evals/content/v2/evals-v2.json`. Trigger cases under `evals/trigger/v2/` are optional and only catch description regressions (positive cases always score 0% — see CLAUDE.md → Gotchas). 6. **`gemini-extension.json`** — CLAUDE.md says Gemini auto-discovers from `skills/`, but the file *also* enumerates each skill+command under `contribution`. If you want that list complete, add `logic-<NAME>` entries to both `contribution.skills` and `contribution.commands`. (Not checked by `validate-repo.sh`.) 7. **Validate** — run `npm run validate` and confirm all checks pass.
Read more
name: new-skill description: 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 missed. Use when adding a seventh (or later) skill to Logic-Lens. disable-model-invocation: true
new-skill
CLAUDE.md → "Adding a New Skill" is the authoritative checklist. This skill exists to make sure *every* step actually runs — the session-start loop and the eval cases are the ones most often forgotten.
**Read CLAUDE.md's "Adding a New Skill" section now**, then execute its steps for `logic-<NAME>` (ask the user for `<NAME>` if not in `$ARGUMENTS`):
1. **`skills/logic-<NAME>/SKILL.md`** — copy the frontmatter shape from `skills/logic-review/SKILL.md` (`name` + `description`). The `description` MUST include a "Do NOT trigger for:" clause and a "SCOPE … RULE" line distinguishing it from the other skills. Process section = 5–7 numbered items, each citing a guide step. Follow lazy-loading per `skills/_shared/common.md` §13. 2. **`skills/logic-<NAME>/logic-<NAME>-guide.md`** — numbered steps (Step 1, 2, …), each explaining the *why*, concrete examples over abstractions. 3. **`commands/logic-<NAME>.md`** — mirror `commands/logic-review.md`:
--- description: <one line> allowed-tools: Skill --- Use the Skill tool to invoke `logic-lens:logic-<NAME>`, then follow its instructions exactly. $ARGUMENTS
4. **`hooks/session-start`** (CLAUDE.md step 6 — easy to miss) — add `logic-<NAME>` to BOTH the `for skill in …` loop and the printed skill list:
grep -n "for skill in" hooks/session-start
5. **Eval cases** (CLAUDE.md step 7 — easy to miss) — add 3–5 content cases to `evals/content/v2/evals-v2.json`. Trigger cases under `evals/trigger/v2/` are optional and only catch description regressions (positive cases always score 0% — see CLAUDE.md → Gotchas). 6. **`gemini-extension.json`** — CLAUDE.md says Gemini auto-discovers from `skills/`, but the file *also* enumerates each skill+command under `contribution`. If you want that list complete, add `logic-<NAME>` entries to both `contribution.skills` and `contribution.commands`. (Not checked by `validate-repo.sh`.) 7. **Validate** — run `npm run validate` and confirm all checks pass.
Logic-first AI code review via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Catches behavioral bugs, type-contract breaches & async hazards that linters miss. Six skills · Claude Code · Codex CLI · Gemini CLI.
Repo: hyhmrright/logic-lens
Other skills on logic-lens.
- /bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when `npm run validate` reports a version mismatch.
Open skill - /iterate-skill
Run the Logic-Lens skill-improvement loop end to end — baseline → diagnose failures → edit → sync cache → re-eval → verify net gain → iterate until clean. Use whenever the goal is to RAISE a skill's eval score or fix a failing eval mode: "improve logic-review", "the format
Open skill - /run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first.
Open skill - /sync-skill-cache
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
Open skill - /logic-diff
Compare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side. Trigger when the user shares a refactor, rewrite, migration, or A/B implementation and wants to confirm behavior is unchanged — "did I break anything", "is this equivalent",
Open skill - /logic-explain
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions). Trigger when the user is confused about behavior or asks why code produces X instead of Y — "walk me
Open skill

