Menú
Initialize Context King in the current repository, or migrate a repo from a legacy per-repo deployment to the global install.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
List files in a folder with their signatures, filtered by an optional regex pattern. Use this in fallback folder-scoped exploration after ck find-files.
Source discovery over path, file, type, and member names. Use this as the default first step before signatures or method extraction.
Build a seed-to-related keyword map from indexed results. Use when file-first retrieval is weak/noisy and you need fallback folder scoping with ck find-files.
Remove a stale knowledge snippet by ID when previously learned context is no longer valid.
Record a new knowledge snippet — domain rules, architectural decisions, gotchas, or cross-module relationships discovered during a session.
Retrieve institutional knowledge for a confirmed folder or a cross-folder semantic query. Step 2.5 in the navigation protocol — run after confirming a target folder, before reading method bodies.
| name | ck-init |
| description | Initialize Context King in the current repository, or migrate a repo from a legacy per-repo deployment to the global install. |
Run once per repository after installing Context King globally. Do not confuse with
ck index (which builds the semantic search index).
Initialize a new repo:
.claude/skills/ck/ck init
Creates .ck.json (minimum version requirement and default findFiles settings), adds .ck-index/ to .gitignore,
and creates the .ck-knowledge/ directory. Commit these files to share the setup
with your team.
Migrate a legacy repo (previously set up with the old per-repo deploy.sh):
.claude/skills/ck/ck init --migrate
Detects and removes per-repo artifacts (binary, model, hook scripts, rule file) and
cleans up relative-path hook registrations and CK allowedTools entries from
.claude/settings.json, leaving all non-CK content intact.
When the user asks for ck init:
ck init directly first..claude/settings.json, .ck, or other legacy artifacts unless:
ck init output indicates legacy deployment conflicts.ck init --migrate when explicitly requested by the user (or after confirming migration is needed from command output).| Option | Description |
|---|---|
--migrate | Remove legacy per-repo deploy artifacts and clean up settings.json |
--force | Re-initialize even if .ck.json already exists |
--quiet | Suppress informational output |
Commit .ck.json and .ck-knowledge/ to the repository. The .ck-index/ directory
is gitignored and will be built automatically on the first ck find-files call.