Use this skill when the user wants to set up knowledge patches for a project or verify which patches match a repo.
Workflow
-
Resolve the project root with:
git rev-parse --show-toplevel 2>/dev/null || pwd -
Scan the project:
python3 ../../scripts/knowledge_patch_setup.py scan --project-root "<project-root>" --format json -
Summarize the detected installable patches and why they matched. Mention that detection is heuristic and the user can also select any available patch manually.
-
If the user did not specify patches to install, ask. Default to all detected patches.
-
If the user did not specify a hook scope, ask whether they want:
repo: write<project-root>/.codex/hooks.jsonso the hook is shared with the repouser: write$CODEX_HOME/hooks.jsonso the hook applies everywherenone: install only the skills
Default to
repo. -
Install the requested patches:
python3 ../../scripts/knowledge_patch_setup.py install --project-root "<project-root>" --all-detected --hook-scope repo --format jsonIf the user selected a subset, replace
--all-detectedwith repeated--patch <name>flags. -
Report:
- installed patch skills
$CODEX_HOME/skillsdestination- hook config path, if installed
- that Codex should be restarted to pick up new skills and hooks
Notes
- Installation is additive. Preserve unrelated skills and unrelated hooks.
- Codex plugins do not currently package hooks through
.codex-plugin/plugin.json. - The helper script installs patch skills from the public
Nevaberry/nevaberry-pluginsrepo, or fromKP_PUBLIC_REPO/--public-repoduring local testing. - The helper script is the source of truth for detection and installation behavior.