knowledge-copilot

Knowledge Copilot — Bootstrapper

Locates the Knowledge Copilot repository on this machine, then hands off to the methodology inside it. This command is a thin bootstrapper; the substantive KMS-building methodology lives in the repo at docs/00-knowledge-copilot/01-build-a-kms.md.

---

Step 1 — Hydrate env vars

eval "$(cc env)"

This populates CC_KNOWLEDGE_REPO (and CC_SHARED_DOCS) if the machine config has a path set.

---

Step 2 — Locate the Knowledge Copilot repo

Resolve REPO_PATH by checking these sources in order; stop at the first hit:

# 1. Canonical env var (set via cc env)
echo "${CC_KNOWLEDGE_REPO:-}"

# 2. Config lookup (in case env wasn't hydrated this session)
cc config get paths.knowledge_repo 2>/dev/null && echo "FOUND_CONFIGURED"

# 3. Generic install location (symlink at ~/.claude/knowledge)
readlink -f ~/.claude/knowledge 2>/dev/null

Set REPO_PATH to the first resolved path. If none resolve, proceed to Step 3.

---

Step 3 — If repo not found: guide the user

The canonical GitHub repo during transition:

• Current name: https://github.com/Everyone-Needs-A-Copilot/knowledge-copilot
• Future canonical: https://github.com/Everyone-Needs-A-Copilot/knowledge-copilot

Ask the user (use AskUserQuestion):

Question: "No Knowledge Copilot repo found on this machine. What would you like to do?" Header: "Setup" Options:

1. "Clone the canonical repo" — ask where to put it (default: a sibling directory next to this project), then git clone [email protected]:Everyone-Needs-A-Copilot/knowledge-copilot.git "$REPO_PATH"
2. "Create a new knowledge repo" — start fresh with guided discovery
3. "Link an existing local repo" — provide a path

After cloning or creating, set REPO_PATH and register it:

cc config set paths.knowledge_repo "$REPO_PATH"
cc config set paths.shared_docs "$REPO_PATH"

Then continue to Step 4.

---

Step 4 — Hand off to in-repo methodology

With REPO_PATH resolved, read the methodology document: