tituskirch-skills-config
tituskirch-skills-config
.tituskirch-skills.json at the repo root is the optional, committed config the other TitusKirch skills read — each setting resolved per repo as config → native → built-in default. This skill owns the file's lifecycle: create it, grow it, reconcile it. It does not own the schema. Every key, type, enum, and default lives once in tituskirch-skills.schema.json — the single source of truth. Read it to validate and enumerate keys; never restate it here or copy defaults into a repo's config. Fetch it raw (curl via Bash) — WebFetch only summarizes and drops the exact enums. Staleness guard — the main URL can be CDN-cached or predate the installed skill, so if the fetched schema lacks a section this skill documents (commit / pr / issue / release / mergeDeps / pruneBranches / docs / work), your copy is stale; re-fetch cache-busted before telling the user a key or section is unsupported.
Jobs — pick by state + intent
| State / intent | Job |
|---|---|
No .tituskirch-skills.json |
setup |
| Config exists, a section absent/incomplete + "add X" | setup (that section) |
| "validate / align / fix / reconcile the config" | reconcile |
| "does the config still match the repo?" — after a rename/add/remove | check (report-only) |
Verb shortcuts: /tituskirch-skills-config setup, /tituskirch-skills-config reconcile, /tituskirch-skills-config check. Otherwise infer from state and the request. Always: plan → confirm → write.
Proactive drift check — some keys point at repo reality (a branch, a template path, a label or team, the skill / package folders behind commit.scopeVocab) and go stale silently when the repo changes. When you add, rename, or remove a skill or package, retarget the integration branch, or change a template or lifecycle label in the same session, run check yourself and offer to reconcile — don't wait to be asked. Trigger on the structural change, not on ordinary edits.