* feat: add Nix flake and stop self-upgrade of Nix-store installs
Add flake.nix with packages, overlays.default, checks and a formatter,
building nix/package.nix with the unit tests in the Nix sandbox. The
version comes from the Release Please manifest, so releases need no Nix
edit. A Nix workflow runs `nix flake check` on non-docs changes.
`skillshare upgrade` now detects binaries under /nix/store/ and prints
`nix profile upgrade skillshare` instead of replacing a read-only store
path; update notices and doctor suggest the same command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(upgrade): give Nix installs the right update path everywhere
The first flake commit sent every /nix/store binary to `nix profile
upgrade`, failed a plain `skillshare upgrade` with exit 1 even when the
CLI was current, and left the dashboard with a generic 500.
- Tell `nix profile` installs (the profile manifest lists the store path)
from NixOS, Home Manager and overlay installs, which are told to update
their configuration and rebuild. Detection lives in one helper shared by
the update notice, doctor, upgrade and the dashboard.
- `upgrade` on Nix reports "already up to date" or prints the hint and
exits 0; the built-in skill still updates.
- The dashboard runs the upgrade so the skill updates, then answers
409 `upgrade.nix` with the command when a newer CLI waits on Nix. The
UI shows localized text for it in all 11 locales.
- Installs skip the unit tests; the flake's checks enable them. postPatch
lowers only the go directive's patch version and fails evaluation with
a clear message when go.mod needs a newer Go minor. CI also builds the
package on macOS.
- Docs, translations, the built-in skill reference and the release topic
describe the new behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Windows temporary paths can use a spelling that differs from the path returned by filepath.EvalSymlinks. Canonicalize test roots before relativizing callback paths and restore internal/sourcewalk to the windows-test allow-list.
* chore(main): release 0.28.0
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.28.0 entry for users
The generated entry listed raw commit subjects, including a docs commit
and an internal skill fix that users never see. Describe each feature
and fix by its visible behavior, with examples and credits, and keep
the website copy in sync.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Feature PRs have arrived with a self-ticked "maintainer approved" box on
issues the maintainer never answered, and with large AI-generated diffs
the author could not stand behind. Make approval a label only the
maintainer can add, and state what an AI-assisted contribution owes
reviewers: an author who has read the diff, answers reviews personally,
does not split changes to dodge the size guideline, and makes only
checkable claims.
Add global project list, show, add, edit, sync and remove so setup scripts
can register repositories without editing YAML or opening the dashboard.
Keep dry runs read-only and report completed work when a target fails.
Reuse the shared project service and sync runners. Include command docs,
translations, completions and regression coverage. Quote overlap hints for
their shell and log partial project syncs consistently with ordinary sync.
SKILLSHARE_CONFIG can select a global config in a directory named
skillshare or .skillshare. Treating it as a project config puts logs and
a .gitignore beside the shared config and labels global logs as project logs.
Exclude selected and read-only global config paths from project routing.
Share the check with the log command so readers and writers agree.
Run the legacy config regression explicitly in Windows CI so it is exercised
without enabling unrelated tests that still need Windows fixes.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore(main): release 0.26.4
* chore(release): synchronize release metadata
* docs(changelog): describe 0.26.4 for users
The generated entry lists commit subjects; users need to know what each change does for them and how to use it.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.26.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.26.1 for users
Replace the generated entry with user-facing notes so the release body
explains what changed in the dashboard and in the tracking guidance.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Correct Unix-only resolution expectations on Windows and pin terminal and renderer state so the package is deterministic. Add theme to the Windows test job to catch future platform regressions. Related to #344.
* chore(main): release 0.25.13
* chore(release): synchronize release metadata
* docs(changelog): write the 0.25.13 entry for users
Replace the generated notes with user-facing descriptions and an example
config for mcp serve skill editing, and drop the Release-As request line.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The windows-test job lists only the packages verified to pass on Windows, so
that the job is green on arrival. internal/memory never reached that list: it
is absent from #344's set of failing packages, and no commit ever added it,
which leaves its 36 tests unrun on the platform whose binaries are published.
Cross-compiled the package's test binary for windows/amd64 and ran it on a
real Windows host: 36 top-level tests passed, 0 failed, exit code 0. The
symlink call sites in store_test.go skip or drop their subcases when the
privilege is missing, so a runner without Developer Mode cannot fail on them.
* chore(main): release 0.25.12
* chore(release): synchronize release metadata
* docs(changelog): write user-facing 0.25.12 notes
The generated entry listed commit subjects only. Describe each fix by what a
user sees: the token in ps, unchanged skills reinstalled by update --all, the
silent fetch failure, missed updates behind symlinks, and the dashboard
breaking after upgrade, with examples and issue references.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.11
* chore(release): synchronize release metadata
* chore(release): write user-facing notes for 0.25.11
Replace the generated commit list with notes that explain what users
see: the MCP pin and tool-change checks with examples, the backup
cleanup fix, and the list detail panel's Targets row. The internal
skills code-review change is left out because it does not reach users.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.10
* chore(release): synchronize release metadata
* docs(changelog): describe 0.25.10 for users
Replace the generated commit list with what changed on the dashboard: Open folder on the MCP page and a project's Agent files on its MCP tab.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.9
* chore(release): synchronize release metadata
* docs(release): write user-facing notes for 0.25.9
Replace the generated commit list with notes that describe each change
from the user's side, with examples, matching the recent entries.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.8
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.25.8 notes for users
The generated entry listed the raw commit subject. Describe the macOS OMP install fix with the message users saw and the command that now works.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.7
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.25.7 notes for users
The generated entry listed raw commit subjects. Describe the OMP version fix and the plugin update dialog fix in the changelog's usual style, with the error users saw and what changed.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.25.4
* chore(release): synchronize release metadata
* docs(changelog): restore the curated 0.25.4 entry and add #511, #513, #515
Release Please regenerated the entry when #513 landed on main. Restore
the user-facing version and describe the three fixes merged since: the
skills source named like a tool folder (#511, via #514), the hidden
agents source folder (#515) and moved installed skills (#513).
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
These packages were left out of the windows-test job because of failures
that came from test assumptions (POSIX paths, permission bits, HOME,
bash shims posing as git), not product behavior. Fix them and add the
packages to the list so they stay green.
Two failures were real product bugs:
- swapStagedIntoSource named its backup like the temp that
sourcefs.MoveIn creates beside it. On a coarse clock (Windows) both
names matched, the failed move removed the temp and with it the
backup, and the old skill was lost.
- MetadataStore.GetByPath looked up OS-native paths in slash-form keys,
so `update --group` missed nested skills on Windows.
The test sandbox now also sets USERPROFILE, which os.UserHomeDir reads
on Windows; tests were reading the real profile.
Refs #344
Ten tests assumed POSIX behaviour:
- Five asserted os.ModeSymlink, but Windows links with a junction;
check utils.IsLinkMode instead.
- Two used `/abs/...` as an absolute path, which has no volume on
Windows; give the fixtures one.
- Windows has no permission bits to preserve, so the 0600 check is
skipped there.
- Reading a file as a directory reports not-exist on Windows, which
prune ignores, so that prune-error test is skipped there.
- A single-file extension relies on the shebang and the executable bit,
so ListExtensions finds only directory extensions on Windows, as the
extras docs describe.
Add ./internal/sync and ./internal/trash to the windows-test package
list so they stay green.
Refs #344
* chore(main): release 0.24.2
* chore(release): synchronize release metadata
* docs(changelog): describe the 0.24.2 download speedup for users
Release Please lists the raw commit subject; the changelog explains user-visible changes in prose with an example, like earlier entries.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.24.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.24.1 for users
Replace the generated commit list with what each change means for users: the memory update modes with the CLI example, the config layout, the Pi project override, the audit config-key fix and the dashboard hooks count.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.24.0
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.24.0 notes for users
The generated entry listed commit subjects, several of them fixes to
features introduced in this same release. Describe what changed from the
user's side, fold those fixes into their features, and give the breaking
init and plain-output changes migration notes.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(design): export dashboard tokens for design tools
Mockup tools read a design system's tokens.json rather than our CSS, so
designs drifted from the dashboard's Clean theme. The script derives the
tokens from components.css, and CI runs its test so a new color
variable without a usage note fails instead of silently going missing.
* feat(plugin): add npm packages from pi.dev through Pi
Pi packages on pi.dev are npm packages, which Plugins could not add:
it only took local or Git sources, so users had to install them with Pi
and import them. `plugin add npm:<package>` now hands them to
`pi install` for Pi targets and records the binding like an import.
Skillshare can't fetch or review an npm package, and Pi runs its install
scripts, so the preview says so, discover refuses npm sources, and only
targets that run pi itself take them. Pi keeps one entry per package
name, so another version replaces it in place and keeps its extension
filters; Skillshare records the new entry so a reinstall restores them,
and refuses a package another Skillshare package already manages, since
removing one would remove both. Pinned versions are skipped on update
because pi update keeps them.
The dashboard accepts npm sources, a pasted `pi install` command or a
pi.dev address, lists only Pi targets, and the Pi Extensions tab links
to adding a package with that target selected. Pi packages show Pi's
mark in the plugin list.
A blocked change now keeps its own reason when the Agent's CLI is also
missing, and the message key always matches the message the CLI prints.
* fix(plugin): keep npm package names and accept pi by path
The default name of an npm package went through the file-path rule, which
cut its last dot segment as an extension: npm:foo.bar was recorded as foo,
and adding npm:foo.bar@1.2.3 later derived foo.bar and was refused as
another package managing the same Pi entry. npm names are now taken from
the package spec.
A Pi account whose CLI is an absolute path to pi was treated as running
another executable, so it could not take npm packages. It now uses the
same path- and platform-aware check as the Pi Extensions tab.
* docs(wiki): add a pull-requests topic for Codex review rounds
Handling Codex's review was only known from practice: confirm each
finding, fix it with a failing test first, reply in its thread, ask for
another review, and follow up until it answers. Writing it down keeps
agents from resolving threads, amending pushed commits, or stopping at
the 👀 that only means the review is still running.
* feat(ui): give the Extras AGENTS.md and Memory tabs one layout
The two tabs shared a page but looked like different products: the header
shifted between them, notes sat in a joined box with an icon toolbar, and
agents showed as an icon strip in a side card. Switching tabs felt jarring.
Memory now follows the AGENTS.md layout: a sticky list column with search,
the note's name with Edit and a More actions menu, the same preview box,
and Use with agents as one row per tool under the note. Long notes open
collapsed like shared files do. The AGENTS.md list gains a search box and
the same sticky column. The Memory tab label stays English in every locale,
like AGENTS.md. Docs and screenshots follow the new layout.
* chore(docs): add a script that serves the Memory screenshot homes
The Memory how-to screenshots came from demo homes that were never
recorded, so reshooting them meant rebuilding the data by hand. The script
rebuilds the fresh and the populated home inside the devcontainer, serves
each behind the Vite dev server, and hands the port back to air afterwards.
* fix(plugin): refuse npm sources Pi can't resolve
validNpmSource accepted specs such as npm:foo/bar, npm:foo@ and names
containing "..", which Pi's own parser rejects. They passed preview, and
Apply recorded a pending binding before pi install failed, leaving an
entry every later sync retried. Validate with the same grammar the Pi
settings reader uses, which also covers a scope without a package name.
* fix(ui): show the default name when adding an npm package to Pi
The name field for an npm source was blank, so it looked like a name was
missing. Leaving it empty records the package name without its version or
scope, as the git flow already shows; the field now shows that name as its
placeholder.
Releases publish windows_amd64 and windows_arm64 archives, and `_windows.go`
files compile only on Windows, yet every job in this workflow runs on Linux or
macOS: a Windows-only regression reaches users at release time instead of at
review.
Start the coverage with the 15 packages that pass on windows-latest today, so
the job is green on arrival rather than a permanent red check. The 14 packages
that fail there are listed in #344 with the failures behind them, and each fix
adds its package back to this list.
-race stays off because the race detector needs a C toolchain on Windows;
ubuntu and macOS already run the raced suite. -count=1 keeps a cached result
from reporting a pass for a package that never ran.
Co-authored-by: Willie <egg358358@gmail.com>
Cursor and Gemini CLI no longer represent the tools most users sync
to, so the demo now shows Pi and Antigravity alongside Claude Code
and Codex, and the regenerated README GIF matches.
The old demo was a dark, slide-like walkthrough of terminal and dashboard
screens. At README width its text was unreadable and it never showed why
anyone would want skillshare. The new demo tells one story in the cartoon
logo's crayon style:
- copies of a skill drift apart
- skillshare keeps one source
- one edit reaches every tool, and a newly added tool gets the setup
straight away
The illustration is drawn in code: crayon grain, navy outlines and the
logo's sync arrows. It needs no screenshots, so it does not go stale when
the dashboard changes.
The crayon grain uses a fixed noise seed. Re-seeding it every few frames
for a hand-drawn "boil" changed every drawn pixel, and the MP4 grew past
GitHub's 10 MB upload limit.
Remotion and React are upgraded to their latest releases. TypeScript stays
on 5.x because Remotion's loader reads tsconfig through `typescript.sys`,
which TypeScript 7 removed.
Present Skillshare around a portable AI coding setup, with aligned README and homepage translations. Replace the public logo and favicon with the approved cartoon artwork and restore navbar spacing.
* chore(main): release 0.23.5
* chore(release): synchronize release metadata
* docs(changelog): describe the 0.23.5 include warning for users
The generated entry listed the two commit subjects. Merge them into one
user-facing fix that explains the symptom, where the warning appears and
what it prints, matching the 0.23.4 entries.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.23.4
* chore(release): synchronize release metadata
* chore(release): describe the 0.23.4 plugin fixes
Replace the generated one-line entry with the user-visible plugin changes and a usage example, in both changelog copies.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>