Menu
Upgrade an existing project's managed llm-wiki structure from Pi without rerunning broad bootstrap.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Upgrade an existing project's managed llm-wiki structure without rerunning broad wiki bootstrap. Use when a user asks to migrate, update, or upgrade project-local .llm-wiki scripts, hooks, or changelog structure after installing a newer llm-wiki release.
Bootstrap an LLM-maintained wiki for the current project. Use when a user asks to create, initialize, or refresh a project wiki, LLM wiki, QMD wiki, or codebase knowledge base for Claude Code, Codex, or Pi.
Check whether llm-wiki is current, detect newer marketplace or Pi package versions, and suggest or run the right update command for Claude Code, Codex, or Pi. Use when the user asks about llm-wiki version, plugin/package updates, marketplace refresh, upgrade instructions, project context setup, or whether a new llm-wiki release is available.
Check llm-wiki install status, version freshness, update commands, and project wiki automation from Pi. Use when a Pi user asks about llm-wiki version, package updates, refresh ownership, context setup, or whether a new llm-wiki release is available.
Bootstrap an LLM-maintained wiki for the current project from Pi. Use when a Pi user asks to create, initialize, refresh, or configure a project wiki, LLM wiki, QMD wiki, or codebase knowledge base.
Plan a feature, bugfix, refactor, or improvement from Pi with wiki research first. Use when a Pi user asks for implementation planning that should include existing project wiki or main cross-project wiki knowledge.
| name | wiki-upgrade |
| description | Upgrade an existing project's managed llm-wiki structure from Pi without rerunning broad bootstrap. |
This is the Pi-safe llm-wiki project-upgrade entrypoint. It uses a prefixed
skill name to avoid collisions with other Pi packages.
Before acting, read and follow the canonical upgrade workflow at
../../../skills/upgrade/SKILL.md.
Pi-specific note: preserve the configured headless_agent; running the upgrade
from Pi does not transfer scheduled or post-commit maintenance ownership to Pi.
