ca-create-context
Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
npx skills add arbiterForge/codeArbiter --skill ca-create-context --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-create-context — brownfield populate Wraps an existing codebase in project state without guessing. Dispatches parallel scouts to read the repository, synthesizes their findings into the surviving `.codearbiter/` doc set, resolves gaps via a targeted interview, and locks the project initialized. No arguments — the skill reads the repo and asks only what it cannot determine. The only permitted path to populate `.codearbiter/` when meaningful source code already exists. For a greenfield project with no source, use `$ca-decompose`. ## Routes to The `context-creation` skill (`${CLAUDE_PLUGIN_ROOT}/routines/context-creation/SKILL.md`) — six gated phases: pre-flight, scout dispatch, synthesis, gap interview, write, lock. Scouts return paths, line numbers, and named values only — never raw source or secret values. The skill is canonical for the phases and their gates. ## When NOT to use - Project already initialized (`<!--INITIALIZED-->` in `CONTEXT.md`) → `$ca-status`. - Greenfield project, no source → `$ca-decompose`. - `.codearbiter/` not yet scaffolded → `$ca-init` first. - Update one doc → edit `<project-root>/.codearbiter/` directly or use `$ca-feature`. ## Hard gate BLOCK if `
- Routes to
- When NOT to use
- Hard gate
What does the ca-create-context skill do?
Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-create-context --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.