← ClaudeAtlas

setup-contextlisted

Set up everything this conversation needs before the work starts - read the current repository (tree, docs, rules files, build, code, git state), search the earlier and archived sessions on this computer (Claude Code transcripts and memory, claude-cluster sessions and their trash, Codex / Qwen / opencode, handover files) for what was asked, done, left and decided, then load the skills that fit the project (style, language, build, tests, docs, git) and check the MCP servers / tools it would use (configured, connected, missing), and hold it all as the working context; the questions only at the end. Use whenever the user says "setup le contexte", "prépare-toi", "charge tout ce qu'il faut", "lis le repo et les anciennes sessions", "setup les skills / mcp utiles", or summons /setup-context before a task.
TsukiNi22/ai-utils · ★ 1 · AI & Automation · score 74
Install: claude install-skill TsukiNi22/ai-utils
# Setup context: the project, its history, the right skills and tools Read what the project is and what was already done, then **equip the session**: the skills loaded, the MCP servers / tools checked. Read-only on the project: nothing built, changed, committed, stopped or resumed. **Scope given with the skill:** the folder / task after `/setup-context` if any, else the cwd and the latest request. ## 1. The project and its history - The `onboard` skill installed: follow its steps 0-4 (the project, its git history, the earlier sessions, merged and checked). Else do the same by hand: - **Tree** (`git ls-files`, sizes, languages), **docs read entirely** (README*, CLAUDE.md / AGENTS.md and the other rules files: rules to follow from now on, CHANGELOG, `docs/`, TODO / NOTES / `.info` / PASSATION.md), **build and CI** (CMakeLists, package files, workflows, hooks), **code** (entry points, module layout, tests, TODO / FIXME). - **Git**: log (recent `--stat`), branches and worktrees, tags, `git status` / diff of the pending work, unpushed commits, stashes (listed, never popped). - Secrets: their existence and place only, never their content. ## 2. Earlier and archived sessions Search by the absolute path of the project (its parents, subfolders, worktrees too), newest first: - **Claude Code**: `~/.claude/projects/<path with every / and . turned into ->/*.jsonl` (worktrees: `<repo>--claude-worktrees-<name>`), its `memory/` (MEMORY.md and its files), `~/.claude/jo