Commit Graph
567 Commits
Author SHA1 Message Date
Willie 0a3e669b09 fix(audit): decouple audit override from Force so --force reaches the gate
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.
2026-08-27 17:10:29 +08:00
Willie 14959e248c chore: release v0.20.25 2026-08-10 10:11:18 +08:00
Willie 04aea45ebd docs: correct Antigravity workaround wording in changelog
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.
2026-08-03 22:46:28 +08:00
Willie c63346be74 chore: release v0.20.24 2026-08-03 21:24:00 +08:00
Willie 9c0200ab2c fix(doctor): make symlink compatibility hint deterministic
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.
2026-08-02 22:39:00 +08:00
Willie 9143b467e0 fix(targets): split gemini out of antigravity and correct global path
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
2026-08-02 22:38:56 +08:00
Willie 1eb54b3e7c chore: release v0.20.23 2026-07-30 01:39:09 +08:00
Willie 262da080c0 docs(backup): document backup scope and disk space, fix stale paths
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
2026-07-30 00:55:47 +08:00
Willie a1e22a7e36 feat(list): add --status filter for non-interactive views
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
2026-07-29 23:23:24 +08:00
Willie 039ec940e9 chore: release v0.20.22 2026-07-21 00:35:19 +08:00
Willie ba46ae8a77 feat(targets): add grok as a built-in target
xAI's Grok CLI reads skills from ~/.grok/skills (global) and
.grok/skills (project), with legacy fallback to ~/.agents/skills.

Ref: https://docs.x.ai/build/features/skills-plugins-marketplaces
2026-07-16 09:30:51 +08:00
Willie e818a29cad fix(collect): preserve overwrite guard in JSON mode
--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.
2026-07-15 09:42:47 +08:00
hhh2210 c5f876c79e fix(uninstall): preserve dirty-repo guard in JSON mode 2026-07-15 09:30:54 +08:00
Willie 67bb2c164f chore: release v0.20.21 2026-06-29 18:39:30 +08:00
Willie 90356071c7 chore: release v0.20.20 2026-06-19 00:25:35 +08:00
Willie d9e3df9fda chore: release v0.20.19 2026-06-17 21:24:27 +08:00
Willie c09968dd6e chore: release v0.20.18
Update changelog surfaces and bundled skill metadata for v0.20.18.
2026-06-16 23:19:58 +08:00
Willie 54ae7b04e2 fix(install): reject project-root self-install via web UI
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.
2026-06-16 10:04:57 +08:00
Willie 5941891eef chore: release v0.20.17 2026-06-15 22:39:44 +08:00
Willie 377faa8b06 chore: release v0.20.16 2026-06-15 13:17:17 +08:00
Willie 451785cf1f chore: release v0.20.15
Update changelog, website changelog, release notes, and built-in skill metadata for v0.20.15.
2026-06-14 16:02:01 +08:00
Willie 5740574af9 chore: release v0.20.14 2026-06-13 22:20:12 +08:00
Willie 3ad54abb6e chore: release v0.20.13 2026-06-11 16:15:25 +08:00
Willie d01a5b2cb4 docs: update v0.20.12 release notes 2026-06-11 01:50:39 +08:00
Willie 060886c281 chore: release v0.20.12 2026-06-11 01:18:10 +08:00
Willie 78b3fc0085 chore: release v0.20.11 2026-06-10 22:37:16 +08:00
Willie ecb31a05a8 chore: release v0.20.10 2026-06-10 16:18:22 +08:00
Willie 10d94a3542 fix: suggest install for missing tracked repos 2026-06-10 15:54:23 +08:00
Willie 63adb16bbb docs: document disabling skills by folder glob
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.
2026-06-09 12:44:30 +08:00
Willie 26ca9f00f8 chore: release v0.20.9 2026-06-05 23:45:36 +08:00
Willie e4ba03334a chore: release v0.20.8 2026-06-05 13:56:07 +08:00
Willie e81b042c55 chore: release v0.20.7 2026-06-03 22:33:11 +08:00
Willie 3966c4df06 docs(changelog): add v0.20.6 entry 2026-06-03 15:45:45 +08:00
Willie 7e391b3648 chore: release v0.20.5 2026-06-03 01:36:01 +08:00
Willie ccbe941291 feat: add Zed editor target
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().
2026-06-03 00:21:29 +08:00
Willie df0817cf57 chore: release v0.20.4 2026-06-02 18:56:25 +08:00
Willie 3306026472 docs(changelog): add extras per-target management and 'extras mode' removal to v0.20.4 2026-06-02 17:42:01 +08:00
Willie e7be4c60c4 docs(extras): sync quick-reference and built-in skill with per-target flags 2026-06-02 17:39:23 +08:00
Willie b0732b75bb docs(extras): document --add-target/--remove-target; drop 'extras mode' subcommand 2026-06-02 17:22:56 +08:00
Willie 1d0ee69955 feat: support SSH hub sources for private and GHE hosts
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
2026-06-02 16:29:25 +08:00
Willie 594a767734 chore: release v0.20.3 2026-06-01 16:31:13 +08:00
Willie 6c29934a4f feat: add agents path to copilot target
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
2026-06-01 15:08:22 +08:00
Willie bc65566f49 chore: release v0.20.2 2026-05-31 23:27:09 +08:00
Willie 85cc972f95 docs(doctor): document suggestions field; refine remediation wording
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
2026-05-31 20:56:37 +08:00
Willie 7ac0431335 chore: release v0.20.1 2026-05-31 13:51:55 +08:00
Willie 1183e0a366 fix: improve codex agent extension validation 2026-05-31 13:39:41 +08:00
Letiancheng Lee ad9ffde242 fix codex agent extension validation 2026-05-31 13:07:25 +08:00
Willie 8df801e21e chore: release v0.20.0 2026-05-30 19:48:52 +08:00
Willie def12c51ca chore: update docs 2026-05-30 19:23:12 +08:00
Willie 314e2b2df4 feat(init): switch git_root scope headlessly on an existing setup
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.
2026-05-30 19:23:12 +08:00