register-context

Promote to Context

You are registering an existing file as context in CLAUDE.md so content skills can discover and load it for future work.

Step 1: Identify the file and target

If $ARGUMENTS contains a file path, use it. Otherwise ask:

"Which file would you like to register as context? (Provide the file path.)"

If $ARGUMENTS also names a target CLAUDE.md explicitly (e.g. "register x in myproject/press/2026/CLAUDE.md"), record that path. An explicit target is a deliberate choice — Step 4 uses it directly, no placement questions asked.

Read the file.

Step 2: Suggest a label

Generate a short, descriptive label (2–5 words) based on the file content. Good labels are specific enough to distinguish this file from similar ones in the same project:

• Too generic: "Writing style"
• Good: "Brand voice – recruiting"
• Good: "Whitepaper – AI in HR (Q3 2025)"
• Good: "Audience – enterprise buyers"

Present the suggestion and ask the owner to confirm or change it:

"Suggested label: [label] (or enter your own — no restrictions)"

Step 3: Generate a summary

Write a one-sentence summary (10–25 words) from the file content. The summary is the key signal skills use to decide which file to load for a given task — be specific:

• Too vague: "Writing style guidelines"
• Good: "Formal German, em-dash preferred, no exclamation marks — all corporate copy"
• Good: "Whitepaper on AI in HR published Q3 2025 — use as reference for follow-up content"
• Good: "Three enterprise buyer personas: CHROs, IT directors, and works councils"

Present the suggestion and ask the owner to confirm or change it:

"Suggested summary: [summary] (or enter your own)"

Step 4: Determine the target CLAUDE.md

If an explicit target was named in $ARGUMENTS (Step 1), use it directly and skip to Step 5 — no placement question, that's the point of naming it explicitly.

Otherwise, scan for candidates:

find . -name "CLAUDE.md" -not -path '*/.git/*' -not -path '*/node_modules/*' | sort