logic-lens

In the author's own words, from each skill's SKILL.md.

• 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", "are these equivalent", "semantically equivalent", "are these two implementations semantically equivalent", "check my r…

  skills/logic-diff/SKILL.md on GitHub (opens in a new tab)

• 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 through this", "trace through X with input Y", "why does this return X", "what does yield-from do here", "explain the exec…

  skills/logic-explain/SKILL.md on GitHub (opens in a new tab)

• logic-fix-all

  Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic issues", "fix all logic issues in this code", "clean up all logic issues", "audit and f…

  skills/logic-fix-all/SKILL.md on GitHub (opens in a new tab)

• logic-health

  Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where should I focus testing", "onboarding review", "logic overview before we ship", "…

  skills/logic-health/SKILL.md on GitHub (opens in a new tab)

• logic-locate

  Locate the root cause of a CONFIRMED failure via backward-then-forward semi-formal tracing. Trigger when the user provides a stack trace, failing assertion, error message, or specific wrong-value observation — "find the bug", "this test is failing", "track down this crash", "why is this test failing", "KeyError at line 89", "expected 70, got 100", "NoneType has no attribute X", "cart empties when…

  skills/logic-locate/SKILL.md on GitHub (opens in a new tab)

• logic-review

  Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this code", "tests pass but prod fails". SCOPE HARD RULE: one file or one function onl…

  skills/logic-review/SKILL.md on GitHub (opens in a new tab)

• 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.

  .claude/skills/bump-version/SKILL.md on GitHub (opens in a new tab)

• 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 compliance is failing, fix it", "iterate on this skill until the evals pass", "raise the score", "re-run the loop on the late…

  .claude/skills/iterate-skill/SKILL.md on GitHub (opens in a new tab)

• 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.

  .claude/skills/new-skill/SKILL.md on GitHub (opens in a new tab)

• 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. Use when the user wants to "run the evals", "score this iteration", "measure the skill change", "smoke-test before the…

  .claude/skills/run-iteration-eval/SKILL.md on GitHub (opens in a new tab)

• 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 grades stale content and every token is wasted. Also use to verify the cache is in sync ("is the cache fresh?", "did my…

  .claude/skills/sync-skill-cache/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• paperclipby paperclipai The open-source app everyone uses to manage agents at work 103k stars · 30 skills
• rufloby ruvnet 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems.… 75.1k stars · 30 skills
• OpenMontageby calesthio World's first open-source, agentic video production system. 12 production pipelines, 100+ tools, 700+ agent skill and production-knowledge… 68.6k stars · 30 skills
• claude-code-best-practiceby shanraisshan from vibe coding to agentic engineering - practice makes claude perfect 67.6k stars · 9 skills
• i-have-adhdby ayghri A skill to stop your coding agent from burying the answer. ADHD-friendly output. 57.3k stars · 1 skill