Repository navigation
skillshare v0.30.12 Release Notes
TL;DR
- Register every Git checkout in a workspace at once with
skillshare project add <root> --scan DIR, or from the dashboard's Add project dialog. - Removing a project says where its MCP and hook settings went.
- MCP server rows show each Agent once, and target pickers fold open instead of popping.
- Removing an OMP plugin no longer fails with "plugin state changed since preview".
Projects: add each checkout in a workspace
Some tools, such as Codex, look for project skills only up to the Git root of the folder you open. When one workspace folder holds several checkouts or worktrees, skills synced to the workspace are not seen inside them. (#953, #958)
skillshare project add ~/work/suite --scan . --scan .worktrees \
--target codex --skills-include 'team-*' -n--scantakes a folder inside the root (.is the root itself) and registers the root and each Git checkout found below it as an ordinary project entry with the same settings, in one write. Hidden folders below a scan folder,node_modulesand links are skipped, so name folders such as.worktreesexplicitly.- It only adds. A checkout already registered with the same settings is kept; one with different settings, its own
.skillshare/, or a name that is already used is skipped with the reason. Rerun it after a new clone or worktree. - A checkout is named after its folder. On a clash the name comes from its path (
.worktrees/app-a→worktrees-app-a) and is saved, so later scans keep it. - A scan folder that does not exist yet or cannot be read is skipped with a warning.
projects_storage,--machine-local,-n,--syncand--jsonwork as for a single add. - In the dashboard, Add project has Also add each checkout inside this folder. Review lists each folder as Added, Kept or Skipped before anything is written, with an Open link for a project whose settings differ.
Thanks to @amphetamlne for the request and for working out the details. See Register every checkout in a workspace.
Projects: removed projects' MCP and hook settings
Removing a project keeps its mcp.projects and hooks.projects entries on purpose, but nothing said so, and the CLI warning gave no next step. (#955)
- The CLI now says, for example,
MCP settings for ~/work/app stay in mcp.projects; remove them on the dashboard's Projects page or in config.yaml. - The dashboard's remove dialog says the settings stay and that removing the leftover row deletes them, except when only this machine's copy goes and
config.yaml's project remains.
Dashboard
- MCP server rows drew the same Agent logos twice, in the count button and as chips under the name. Rows now keep only the count button; opening it shows the toggles with each Agent's name, and Pi's exposure mode is a tag beside the Pi toggle. (#952)
- The target pickers of MCP rows, MCP defaults, plugin rows and a project's MCP tab fold open and closed, and stay still for people who ask for reduced motion. A project's MCP Targets now reads like the global defaults: while it inherits, the global targets show ticked, the first tick starts its own list from them, and Back to global returns after a confirm. (#952)
Plugins
- Removing an OMP plugin while other OMP plugins were registered could fail with "plugin state changed since preview", because the preview read their package files in a different order each time. (#949)