chrome-session-helper

OnRush-Plugins

A Claude Code plugin marketplace for OnRush Studio. One repo, multiple plugins, plus a popup-driven manager so you can pick which plugins are active in each project without typing terminal commands.

What's in here

Plugin	What it does
onrush	An /onrush-setup skill (alias /ors-setup) that opens a popup checklist of the other OnRush plugins and enables/disables them for the current project — the popup is the installer, no terminal commands. Plus /onrush-update (alias /ors-update) to pull the latest plugin code and refresh this project's vendored copies.
github-commits-manager	SessionStart + Stop hooks that remind you to commit changed files at the end of a session, using a per-session baseline so only this session's edits are flagged. Toggle it with /github-commits-manager:config.
chrome-session-helper	A SessionStart hook that launches Chrome so browser-based tools are reachable. No-op if Chrome is already running.

Install

/plugin marketplace add MetaHumanREAL/OnRush-Plugins
/plugin install onrush@onrush-plugins

Then, in any project, run:

/onrush-setup

…and tick the plugins you want active in that project. The manager writes your choices into the project's .claude/settings.json under enabledPlugins, so each project keeps its own set. Reload the session afterward so newly enabled hooks/commands load.

You can also install plugins directly if you prefer:

/plugin install github-commits-manager@onrush-plugins
/plugin install chrome-session-helper@onrush-plugins

Two layers of control

• Which plugins are on in this project — handled by onrush (writes enabledPlugins in the project's .claude/settings.json).
• Settings inside a single plugin — handled by that plugin's own config command. e.g. github-commits-manager reads .claude/onrush-commits.config.json ({ "enabled": true, "includeRegex": "" }); its hooks self-disable when enabled is false, and includeRegex (an extended regex on the file path) narrows which files it watches.

Repo layout

OnRush-Plugins/
├── .claude-plugin/
│   └── marketplace.json          # lists every plugin below
├── onrush/
│   ├── .claude-plugin/plugin.json
│   ├── scripts/onrush.py         # deterministic install/update helper
│   └── skills/                   # /onrush-setup, /onrush-update (+ /ors-* aliases)
├── github-commits-manager/
│   ├── .claude-plugin/plugin.json
│   ├── hooks/hooks.json          # SessionStart + Stop
│   ├── hooks/snapshot-baseline.sh
│   ├── hooks/check-inscope-commit.sh
│   └── commands/config.md
└── chrome-session-helper/
    ├── .claude-plugin/plugin.json
    └── hooks/{hooks.json,ensure-chrome.sh}

Adding a new plugin

1. Create your-plugin/.claude-plugin/plugin.json (only name is required) plus its commands/, hooks/hooks.json, skills/, etc. at the plugin root.
2. Reference hook scripts with ${CLAUDE_PLUGIN_ROOT}/hooks/<script>.sh in hooks/hooks.json.
3. Add an entry to .claude-plugin/marketplace.json (name, source: "./your-plugin", description).
4. Add it to the catalog in onrush/skills/onrush-setup/SKILL.md so it shows up in the picker.

Things to verify on first use (Claude Code version-dependent)

• ${CLAUDE_PLUGIN_ROOT} on SessionStart/Stop. Some Claude Code versions have not reliably injected this variable for the SessionStart/Stop events. If the hooks don't fire, that's the first thing to check. (The scripts themselves don't depend on the variable for their logic — they cd to the consuming project's git root — it's only used to locate the script files.)
• In-repo source syntax. This marketplace points each plugin at an in-repo subdirectory via "source": "./plugin-dir". If your Claude Code version wants the object form instead, use "source": { "source": "local", "path": "./plugin-dir" }.
• Per-project enable via enabledPlugins may require a session reload to take effect.
• permissions.allow cannot ship in a plugin. If a hook needs a permission grant, the installing project/user grants it the first time it runs.

Notes

• Hooks are bash scripts; they need bash available (Git Bash/MSYS2 on Windows, native elsewhere) plus git, awk, sort, comm, grep. jq is used if present, with a fallback. .gitattributes forces LF endings on *.sh so they don't break on Windows.