Run any Skill in Manus with one click

bump-version

Stars11

Forks1

UpdatedMay 28, 2026 at 14:43

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hyhmrright

hyhmrright/logic-lens

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	bump-version
description	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.
disable-model-invocation	true

bump-version

Logic-Lens keeps the version in six places (see CLAUDE.md → Version Sync). Hand-editing them drifts; validate-repo.sh only detects drift. This skill rewrites all six atomically via scripts/bump-version.py.

Steps

Pick the target version. If the user passed one in $ARGUMENTS, use it. Otherwise read package.json's current version and ask whether to bump patch / minor / major.
Run the bump from the repo root:
```
npm run bump-version -- <new-version>     # e.g. npm run bump-version -- 0.7.0
```
It rewrites the version field in package.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, .codex-plugin/plugin.json, gemini-extension.json, and the README.md badge — preserving formatting — then runs validate-repo.sh.
Confirm the run ends with "All checks passed." If any file is reported as a mismatch, stop and report which one — do not hand-edit around the script.
CHANGELOG.md is not touched. For a real release, add a CHANGELOG.md entry for the new version yourself.

More from this repository

same repository

iterate-skill

hyhmrright/logic-lens

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 latest failures", "run another iteration", "tune the skill description / disambiguation table against the evals". Also use to RESUME a prior loop ("continue improving from where we left off", "do another pass", "iterate further"). Do NOT use for: a one-off question about a skill, shipping a release (use bump-version), or scaffolding a brand-new skill (use new-skill).

2026-06-0111

run-iteration-eval

hyhmrright/logic-lens

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 full run", or "re-grade existing outputs".

2026-06-0111

sync-skill-cache

hyhmrright/logic-lens

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").

2026-06-0111

logic-review

hyhmrright/logic-lens

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 only. For a directory or whole module use logic-health; for a confirmed failure (stack trace, failing test, specific wrong value) use logic-locate; for two versions use logic-diff; for repo-wide autonomous fixing use logic-fix-all. Do NOT trigger for: style/formatting, security scanning, performance, test generation, architecture or design questions.

2026-05-3011

new-skill

hyhmrright/logic-lens

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.

2026-05-2811

logic-diff

hyhmrright/logic-lens

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 refactor", "same behavior after the change?", "does my rewrite produce the same output", "switched from X to Y — same results?". SCOPE HARD RULE: requires two code versions (A and B). A single version for bug-finding uses logic-review; one version + a failing test uses logic-locate; explaining what one piece of code does uses logic-explain; codebase audit uses logic-health. Do NOT trigger for: single-version review, performance comparison, design-quality comparison, or "which is better-written" questions.

2026-05-1511

name	bump-version
description	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.
disable-model-invocation	true

bump-version

Steps

Pick the target version. If the user passed one in $ARGUMENTS, use it. Otherwise read package.json's current version and ask whether to bump patch / minor / major.
Run the bump from the repo root:
```
npm run bump-version -- <new-version>     # e.g. npm run bump-version -- 0.7.0
```
It rewrites the version field in package.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, .codex-plugin/plugin.json, gemini-extension.json, and the README.md badge — preserving formatting — then runs validate-repo.sh.
Confirm the run ends with "All checks passed." If any file is reported as a mismatch, stop and report which one — do not hand-edit around the script.
CHANGELOG.md is not touched. For a real release, add a CHANGELOG.md entry for the new version yourself.