InstallOptions.Force carried two meanings: "overwrite what is already
there" and "proceed despite audit findings". Update paths set Force
unconditionally to overwrite a staged temp dir, so they had to leave it
off to keep the audit gate alive -- which swallowed the caller's --force
and made the gate impossible to override from either the CLI or the web
UI.
Split the audit intent into InstallOptions.AuditOverride and route every
gate through it alone. Entry points translate --force explicitly, so a
missed one degrades to "force has no effect" rather than "audit is
bypassed". Scan failures stay fail-closed regardless: accepting known
findings is not the same as being unable to learn any.
This also closes two paths that bypassed the gate outright, since both
inherited Force for overwrite reasons alone: install --json and grouped
batch updates.
In the web UI, Force Retry now appears only on failures force can
actually resolve -- a permission-denied unlink previously offered a
button that could never succeed -- and CLI-only flag hints are stripped
from messages rendered there.
Behaviour change: a --force at install time no longer exempts later
updates from the audit gate; it is a one-off decision per command.
The v0.20.24 entry described the second workaround as symlinking the
whole skills directory, which is not what the troubleshooting docs
recommend. Point at Antigravity's Skill Custom Paths setting instead,
so the changelog matches common-errors.md.
The hint picked its example target by ranging a map, so the same config
produced a different suggestion on each run, and it could name a target
whose runtime handles symlinks fine — telling users to change something
that was not broken. Restrict the choice to the targets known to skip
symlinked skill directories, in the documented priority order.
Also correct the sync docs: the hint is printed by doctor, not sync.
Antigravity and Gemini CLI read different global skill directories, so
folding gemini into antigravity as an alias made one of them wrong for
every user. Antigravity loads ~/.gemini/config/skills; Gemini CLI loads
~/.gemini/skills. Restore gemini as its own target so both resolve
correctly.
Also document that Antigravity's skill scanner skips symlinks entirely
(surfacing as "Incorrect function" on Windows, silent absence elsewhere)
along with the two available workarounds.
Closes#255
The backup docs claimed per-skill symlinks were "resolved and followed" and
their real content backed up, which is now the opposite of what happens.
Adds a Backups & Disk Space section contrasting the three mechanisms that are
easy to conflate — .gitignore (git only), ignore: (sync), and backup (local
target content) — plus an ENOSPC troubleshooting entry, since disk space had
no coverage anywhere in troubleshooting despite being how this surfaced.
Also corrects two long-standing errors: the backup location was documented
under ~/.config in the built-in skill reference and in a `backup --list`
example, but backups live in the XDG data dir (config.DataDir()); and the
built-in skill claimed backup was global-mode only, when project mode does
support agent backups.
Refs #252
The enabled/disabled filter existed only inside the list TUI (`s` key,
`status:` search tag), so scripts had no way to ask for one status. They
had to know that `disabled` is omitted for enabled entries and filter the
JSON themselves; plain-text callers had to parse the `[disabled]` label.
`--status all|enabled|disabled` exposes the same concept outside the TUI.
`all` is normalized to an empty filter at parse time, which keeps the
default output, the JSON array shape, and the tracked-repositories summary
byte-identical to omitting the flag. Status combines with the pattern and
--type using AND semantics, and works in project mode and for agents.
The TUI still loads both enabled and disabled entries; --status only seeds
the initial `Status:` chip, so `s` can cycle back to All.
Implements proposals/244-list-status-filter.md.
Closes#244
--json implied --force, silently overwriting existing skills/agents
in source when collecting. Decouple confirmation-skip from the
overwrite guard, same fix as PR #243 for uninstall.
The project-root self-install guard lived only in the CLI handler, so the
web UI could still copy the project root into its own .skillshare/skills/
subtree in project mode. Extract the check into a shared
install.RejectProjectRootLocalInstall and apply it in handleInstall and
handleInstallBatch, returning 400 with the same guidance.
Also restructure the rejection message into a cause line plus an
actionable "Run '...'" hint, matching the project's error convention.
Surface the existing .skillignore glob support in the enable/disable
command reference and the folder-organization guide. Users reported
(issue #209) only finding it buried in reference/filtering, assuming
disable accepted skill names only.
Add "frontend/**" folder examples, a dedicated "Disable a Whole Folder"
section, and shell-quoting guidance.
Zed added agent-skills support in vercel-labs/skills v1.5.8, using the
universal ~/.agents/skills (global) and .agents/skills (project) paths with
a flat-only skill layout. Register it as a built-in target and document it.
Since Zed shares the universal .agents/skills project path, it is auto-grouped
under the universal target by GroupedProjectTargets(); the docs note reflects
this. Verified in devcontainer: internal/config tests pass and zed resolves
via KnownTargetNames().
Hub index fetch previously handled only unauthenticated HTTP(S) GET or
local file paths, leaving private and GitHub Enterprise repos out of
reach — raw HTTPS URLs redirect to login before token headers apply, and
SSH-style hub URLs were unrecognized.
Resolve SSH hub sources by shallow-cloning the repo with the user's SSH
keys and reading the index from it. The in-repo index path uses the
existing //path subdir convention (consistent with `install`), defaulting
to skillshare-hub.json at the repo root. Both scp-style and ssh:// URLs
are accepted. In the web dashboard, SSH clones are restricted to saved
hubs so a request-supplied URL can't drive an arbitrary clone.
Ref #185
Copilot CLI uses the same .agent.md format Skillshare already syncs to
Claude and OpenCode, so no transformation is needed — only a missing
registry path. Add global (~/.copilot/agents) and project (.github/agents)
agent paths per GitHub's documented custom-agent locations.
Closes#184
Follow-up to eb99118d (doctor overlap suggestions):
- Document the optional `suggestions` JSON field in doctor.md with an example
- Clarify shared-paths wording: the listed targets are all current collisions, not "the others"
- Print the cross-target suggestion after overlap detail lines for a more natural read order
Previously 'skillshare init --git-root <scope>' on an already-initialized
setup either errored with 'already initialized' (no --remote) or warned and
ignored the flag (with --remote), so there was no non-interactive way to
change the scope after init — only the web UI or a manual config edit.
handleExistingInit now treats 'init --git-root <scope>' (without --remote) as
a headless scope switch via switchGitRootScope: it inits a repo at the new
scope directory (reusing one already there, sharing doGitInitIfAbsent with the
fresh-init and server paths) and persists git_root. It does not relocate an
existing repo — switching scope means 'version a different directory', not
'move history'. Combined with --remote the flag still falls through to the
remote path, now pointing users at the standalone form instead of a bare
'ignored' warning.
Update the mismatch guidance to offer 'skillshare init --git-root <scope>' as
the first fix, and revise the git_root docs (configuration + init) to document
the headless switch, superseding the earlier 'must re-run init / not supported'
wording. Add TestGitRoot_SwitchScopeAfterInit.