← ClaudeAtlas

init-workspacelisted

Initialize or refresh this project's CLAUDE.md with accurate context about the repositories, architecture, and knowledge packs. Run on the first session and after significant workspace changes.
alergyonthestage/claude-orchestrator · ★ 4 · AI & Automation · score 80
Install: claude install-skill alergyonthestage/claude-orchestrator
# Init Workspace: Project Context Initialization Initialize or refresh the project's CLAUDE.md with accurate, up-to-date context. The rich project narrative lives in CLAUDE.md (authored here). Structured resource descriptions have a single home — `project.yml` — and are optional; you can only write them when the session has `cco_access ≥ edit-project` (see the final section). ## Scope Parse `$ARGUMENTS` (default: `all`): - `repos` — explore repositories and update their sections only - `packs` — describe knowledge files only - `all` — do everything ## Step 1: Read the session context Your session already carries an injected **cco session-context block** (`<CcoSessionInfo>`, added at startup) describing the project structure: repos (container paths at `/workspace/<name>`, with optional descriptions), packs, knowledge files (indexed pack knowledge with paths + descriptions), llms (official framework docs), extra mounts, and — when `show_host_paths` is on — a host↔container path map. Use it as your inventory. Read `/workspace/project.yml` for the authoritative, structured resource list (repos, packs, llms, extra_mounts) and any existing `description:` fields. You can also query more on demand with the wrapped `cco` CLI (`cco list`, `cco project show`) when the session's access scope allows it. ## Step 2: Explore repositories and shared libraries (scope: repos or all) For each repo listed in the session context / `project.yml`: 1. Read `README.md` (or `README`) — get the