mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 20:34:19 +00:00
The panel read skills, agents, MCP servers, plugins and hooks, but not extras, which `sync --all` also syncs. An extra waiting for a sync was not shown, so Overview could say everything was in sync when it wasn't. Extras are now a sixth kind, read per scope with `extras list --json` and `extras memory list --json`. Overview counts them, and an extra whose target is not `synced` waits for a sync like an MCP server, so the existing Sync button covers it. Library has an Extras tab with file extras, folder extras and memory notes. A preview shows the file, or a folder's files, with its frontmatter, and the targets with their mode and status. Nothing new can be changed from the panel. An extra's target is named by the target whose skills folder shares its parent folder, as the dashboard names it, else by its path. In a project, `status` reports absolute target paths while extras keep the config's relative ones, so those are resolved against the project folder first. Targets that share a skills folder, such as codex and universal at ~/.agents/skills, come from `status` in no fixed order, so the first by name names the extra's target. An extra whose source is missing (`source_exists` is false, or a target reports `no source`) is not something a sync can fix: `doctor` reports it as an error, `diff` marks it failed and the dashboard shows it in red. It goes under Need a look as "source missing", which now holds more than hook notices, so Overview's title for it is "NEED A LOOK". With nothing waiting, Overview says how many extras need a look instead of "Everything is in sync", and the preview says the source is missing instead of offering a Try again that can't help. Memory notes never wait for a sync, so a failed memory read, as on a CLI before 0.24, leaves the sync state confirmed and Sync available. When that read has never answered, the Extras count is the extras that were read. The memory folder also appears as an extra of its own, as it does in the dashboard's Folders & files. Refs #930 * fix(herdr): keep missing-source extras on Overview and list only synced files Review of #961 found two gaps. While extras were read again, or after `extras list` failed, a missing-source extra turned "unknown" and was shown neither under Need a look nor under Sync status unconfirmed. It now waits under Sync status unconfirmed, like other rows whose read is pending. A folder extra's preview listed its files with the skill reader, which skips only the top-level .git. Extras sync skips every .git folder and every .metadata.json (DiscoverExtraFiles), and .metadata.json sorted first, so it could open as the default document. The preview now lists the folder as extras sync sees it. Refs #930
skillshare Wiki Router
The wiki stores development background, procedures, references, and history, but no task needs all of it at once. Rules that apply to every task live in the root AGENTS.md. wiki/ai-context.json is the only source of truth for topic-to-source mappings.
python3 scripts/ai-context.py list
python3 scripts/ai-context.py <topic>
Task Routing
| Topic | Use when | Main sources |
|---|---|---|
architecture |
Tracing repository structure, data flow, or CLI/Web API boundaries | architecture.md |
cli-development |
Adding or changing Go CLI commands, flags, handlers, TUIs, or mutating behavior | cli-development.md |
testing |
Building, testing, reproducing bugs, or using the devcontainer/ssenv | testing.md, CONTRIBUTING.md |
e2e-runbooks |
Writing or running ai_docs/tests E2E runbooks, or verifying on a Windows guest |
e2e-runbooks.md |
frontend |
Changing React, CSS, layout, or visual behavior in the dashboard or website | frontend.md, website/AGENTS.md |
herdr |
Changing the native Herdr panel, gallery packages, or layout integration | herdr.md, herdr/AGENTS.md |
documentation |
Updating README files, website docs, flags, translations, or the built-in skill | documentation.md, CONTRIBUTING.md |
release |
Writing changelogs or release notes, bumping versions, tagging, or releasing | release.md |
audit |
Running read-only consistency audits | audit.md |
pull-requests |
Opening a pull request or handling its review comments, including Codex review | pull-requests.md |
ai-context |
Maintaining router topics, budgets, and orphan checks | ai-context.md |
Run python3 scripts/ai-context.py check after changing topics. This table is the human entry point; the JSON configuration controls what the loader renders.
History (Milestone Logs; Read on Demand)
Completed milestones are recorded here and read only when relevant.
| File | Contents |
|---|---|
| OMP native support | Native MCP/Hooks, safe Extension selection, bounded Plugin support and shared-cache blocker |
| Shared memory notes | Shared Markdown source, CLI/API/dashboard, recent notes, trial/organization prompts, versioned edits and native memory boundaries |
| Git hooks management | Config-mode destinations, includes, ownership, native verification and execution limits |
| Native hooks management | Native formats, CLI/dashboard scope, ownership and verification evidence |
| MCP: Pi built-in only and tool policy | 0.23.0 Pi migration, per-Agent tool policy translation, evidence and limits |