Add target and the Edit target dialog each implemented the field rules
(an extension forces copy, symlink turns flatten off), and they had
drifted: the dialog kept flatten on through a switch to symlink and
back. applyDraftChange now holds the rules and both use it, so the
dialog clears flatten on symlink exactly like Add target.
Refs #490
The extras diff, list, status and remove-target commands and the
server's list and diff handlers each discovered an extra's source and
then filtered it with ExtraTargetFiles. A new view that forgot the
filter step would silently show the wrong file count or status.
DiscoverExtraTargetFiles now discovers and filters in one call and
returns the unmatched-include warnings that sync reports. Every caller,
including sync itself, uses it, and ExtraTargetFiles is gone. No
behavior change.
Refs #487
cmdExtrasMode only ran ValidateExtraConfig behind a growing list of
conditions, so each new restriction needed another clause. For a plain
folder extra the full check adds only the mode-name and flatten+symlink
rules, which sync already rejects, so validating unconditionally cannot
refuse a config that syncs today.
The agents and memory extra names were string literals in sync, the
server handlers, the memory store, and the CLI. They now live in
internal/config, and the rename guard moves to ValidateExtraRename so a
future CLI rename reuses it instead of copying the check.
Refs #489
The rules "an extension forces copy mode" and "symlink mode drops
include/exclude" were re-implemented in the create, edit-target, and
quick mode handlers. ExtraTargetConfig.EffectiveMode and Normalize now
hold them in one place, and the handlers call those instead. API
behavior is unchanged: edit-target still clears filters on symlink,
quick mode still rejects symlink when the target has filters, and an
extension still forces copy.
Refs #488
syncExtraDir took ten positional arguments, three of them bools, and
CollectExtraFiles took nine. Every new target field meant changing each
signature and every call site, and swapped bools compiled silently.
Both now take the target as config.ExtraTargetConfig plus an
ExtraSyncOptions for dry run, force and project root; SyncExtraTarget
takes the same options. The SyncExtra wrapper only served tests, so it
is gone and the tests call syncExtraDir directly. No behavior change.
Refs #486
- On a multi-target extra, `extras <name> --flatten --add-exclude ...`
without --target took the flatten-for-all-targets path, which returned
before the filter flags were applied, and still reported success. Filter
flags now require --target there, like --mode.
- The `extras list` TUI mode picker saved a mode without validation, so a
filtered target could be switched to symlink and break every later sync.
The change is now validated before saving.
Refs #435
- Pointing a symlink-mode extra at a new source after its old folder was
moved or deleted left the target broken: the old link no longer resolved,
so it was not recognised as ours, and the next sync skipped it as pointing
elsewhere. The link text is now compared with the old source as well.
- A negated include such as "!draft.md" only narrows earlier rules, so on
its own it never matches and was always reported as matching no file.
Negations are no longer checked for matches.
Refs #435
- Sync validation skipped directory extras, so a malformed include such as
"[" written in the config matched nothing and merge sync pruned every
link. Extras with include/exclude now go through ValidateExtraConfig.
- The dashboard's quick Mode menu could switch a filtered target to symlink
and save filters that every later sync rejects. That change is now
validated with the target's filters and refused.
- Changing an extra's source removed the links into the old folder before
saving the config, so a failed save left working targets broken. The
config is saved first.
Refs #435
Every submenu trigger closed whichever submenu was open when its 180ms
leave timer fired. Moving from Mode to Flatten and back let Flatten's late
timer close Mode's submenu a moment after it opened. A trigger's timer now
closes only its own submenu.
A directory extra used to sync every file to every target, so a tool that
only wanted a few docs got the whole folder. Each target can now set
gitignore-style include/exclude patterns, matched on the path inside the
source. Merge targets prune links to files that stop matching; copy targets
keep earlier copies, since nothing records which copied files are ours.
Filters are rejected for symlink mode and single-file extras, and sync warns
when an include matches nothing.
The dashboard previously forced users to delete and re-add a target or an
extra to change it. Edit target now changes the folder, file name, mode,
flatten and filters with a live preview; Edit extra renames an extra or
points it at another source folder. A moved target or source drops the
links left at the old place and syncs right away.
CLI: --include/--exclude on extras init, and --add-include, --add-exclude,
--remove-include, --remove-exclude on extras <name>.
Refs #435
The pull response copied only the sync's warnings, so with unmatched
include filters moved to their own field, the Git Sync page stopped saying
that a filter selected nothing after its automatic sync. The pull response
now carries them and the page shows the same notice as the Sync page.
When a followed source link cannot be read, the skill list is partial and
pruning is already skipped. Reporting a filter as unmatched in that state
told users the target gets no skills and sent them to edit a filter that
may be fine.
The project sync dialog and the sync preview modal show only the response's
warnings. With unmatched include filters moved to their own field, a sync
from those dialogs no longer said that a filter selected nothing. Both now
render the same notice as the Sync page.
Two global targets with the same unmatched filter were merged into one
notice whose Edit filter link opened only the first target, leaving the
other unfixed. Only a project's targets share a filter, so other targets
now keep their own notice and link.
A target whose includes were an unmatched pattern plus a blank entry was
not marked as getting no skills, because the check counted the raw list
while filtering drops blanks. It now counts the effective patterns.
The dashboard showed the CLI's raw line, "api-server@claude: include pattern
"*review*" matches no skill in the source", once per target. It named a
config field, did not say the target ends up with no skills, and gave no way
to fix it. Sync now returns these as structured entries; the Sync page
groups a project's targets into one localized notice that says what happens
and links to where the filter is edited. The CLI line also says the filter
adds nothing to the target.
The Sync button sat in the sticky bar and the last-sync card started below
it, leaving the right column misaligned with the page header. The buttons
now sit on the card, which sticks with them, so Sync stays visible while the
change list scrolls. The Include bar keeps tight gaps at rest, gets more room
and a bottom line once it sticks.
A collapsed group's items still used up the 100-item page, so later groups
stayed hidden behind Show more and the footer counted rows nobody could see.
Tracked repos are now named owner-repo, so repeating `install --track` for a
repo cloned earlier as _<basename> went to a new _owner-repo path and cloned a
second copy whose skills collide during sync. When that older checkout has
the same remote, keep using its name so the install skips as the same repo.
Check statuses persist in one non-expiring localStorage entry shared by every
dashboard on the origin. A restored stale status could offer Prune for a
skill reinstalled since, or one in another project, and prune force-moves it
to trash. Stale is no longer restored from the cache, so Prune only appears
after a check in the current session.
Newly installed skills had no target entries in the cached matrix while the
Skills page kept it mounted, so the Sync page could hide Discard all for them
until the cache went stale.
The sync item grid indexed rows by display path, so a skill "reviewer" and
an agent "reviewer.md" collapsed into one entry while the header still
counted two changes. Keep every row under a shared path.
Statuses were stored under the skill's basename, so a/foo and b/foo shared
one entry. With Prune all acting on stale statuses, a stale b/foo also marked
a/foo stale and both would be sent to trash. Key statuses by relative path
and bump the cached format so old name-keyed entries are dropped.
The dashboard's install-from-config context read the global skills source
from s.cfg, which stays global in project mode. Missing entries were checked
against the global folder and installed there instead of the project's
.skillshare/skills. Use the project-aware skillsSource and reload the
metadata store from that same folder before reconciling.
Uninstalling any skill of a tracked repo removes the whole repo, so when a
repo update brought one new skill while its siblings were already synced,
Discard all would have trashed the synced siblings too. A repo now qualifies
only when every skill in it has never been synced.
The maintainer wants these changes shipped as a patch on the 0.25 line
rather than the 0.26.0 that the feat commits would otherwise propose.
Release-As: 0.25.3
The sync matrix marks symlink-mode targets `na` because filters don't apply,
so Discard all ignored them when deciding whether a skill had ever been
synced. A skill pending only for a merge target while already live through a
symlinked one was offered for discard, and trashing it would also pull it
from the symlinked target. Count those targets as receiving every skill.
Installing what config records still needed the CLI, and skills deleted
upstream showed as updates with nothing to update. The Update page and
install dialog now offer Install all for missing entries, and stale skills
get Prune / Prune all, which move them to trash in one request.
A sync of hundreds of changes was a wall of identical rows per target. Sync
now groups targets that receive the same changes into one card listing names
by folder, keeps its action bar and summary sticky, and adds Discard all,
which moves skills that were never synced anywhere to trash after a
confirmation. The Skills page keeps its toolbar and group heads in view while
scrolling, folds New skill and Link folder into the Install menu, remembers
filters in the browser, and moves Update repo into the repo menu.
Bare `skillshare install` already restores everything .metadata.json records
but the disk lacks, yet the dashboard could only re-clone missing tracked
repos through a separate rehydrate path. Expose the CLI's install-from-config
flow instead (GET /api/install/missing, POST /api/install/from-config) so both
surfaces share one detection and one installer, and drop the old
missingTrackedRepos plumbing from update responses.
The install summary now counts tracked repos and their skills apart from
standalone skills, since "Installed 1 skill" hid a whole repo. New tracked
repos are named `_<owner>-<repo>` so two `skills` repos no longer collide;
existing installs keep their names. `check` passes the stale status through
so the dashboard can offer to prune skills deleted upstream.
The generated entry listed each fix twice (a merge commit and its source
commit share a subject) and only named commits. Group the fixes by area,
say what changed for the user with examples, and note that overrides
for prompt-injection-4 do not carry over to prompt-injection-5.
The 0.25.2 fixes changed behavior the command pages still described
the old way: update said any .git/ directory makes a tracked repo, the
uninstall Project Mode section missed --into repos and the refusal
inside a tracked repo, and the audit rule table lacked
prompt-injection-5. Also translate the uninstall example comments that
were left in English in ja, ko, zh-Hans and zh-Hant.
Every entry Skillshare manages was titled "Plugins · <name>" with a box
icon, so Pi packages installed through the Plugins page looked like
plugins. The tab now splits them the way the Plugins page does
(piPackageTest): a Pi package reads "Package · <name>" with Pi's black
and white mark, and a plugin reads "Plugin · <name>" with the box icon.
Keep the built-in skill analyzer list aligned with the audit parser and website documentation.
Validated the five-locale website build, context-router check, and diff checks.
Reuse the shared tracked checkout resolver after checking the typed path so uninstall org/team finds org/_team without taking precedence over an existing skill or folder. Classify tracked targets by the underscore checkout rule across CLI uninstall entry points, retaining ambiguity errors and the shared inside-repo refusal.