Files
skillshare/wiki
Willie 769087b882 fix(project): keep config.yaml true after reinstall, uninstall and fresh-clone installs (#860)
In project mode the committed config.yaml is what teammates install from, but
it could disagree with what a machine actually has (#858):

- `uninstall -p` and the dashboard's single-skill and tracked-repo removal
  left the skill's entry in config.yaml, so a later `install -p` brought it
  back. They now drop the entry and the lock pin through one shared
  config.ForgetProjectSkills, as the uninstall docs already promised.
- Installing a skill again from another source or branch (after an uninstall,
  or over the copy with --force) updated only the gitignored .metadata.json.
  config.yaml kept the old source and skills.lock.json ended with the old
  source and the new commit. Installs from a named source (CLI install,
  search, dashboard) now compare the records from before and after the
  command and let the config entry follow the skills it actually reinstalled.
  Install from config never rewrites an entry from local records, so a
  teammate's edit survives on a machine that has not updated yet.
- Reconcile removed every config entry that had no folder and no record. On a
  fresh clone nothing is installed yet, so `install <source> -p` deleted all
  the other declared skills. An entry now goes only when the skill was
  installed here and its folder is gone, when it was moved, or when a command
  removed it; `move` passes the old paths and `update --prune` cleans the
  config itself.
2026-11-11 22:42:03 +08:00
..

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