8765ba4324
Gathers CLAUDE.md, CONTEXT.md, MEMORY.md, BESTPRACTICES.md, directory trees, and git status from the directory hierarchy after /clear. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.8 KiB
1.8 KiB
name, description, user_invocable, allowed-tools
| name | description | user_invocable | allowed-tools |
|---|---|---|---|
| context-load | Reload project context after /clear or mid-session. Runs the context-load script to gather CLAUDE.md, CONTEXT.md, MEMORY.md, BESTPRACTICES.md, directory trees, and git status from the directory hierarchy. Use when context has been lost (e.g., after /clear). | true | Read, Glob, Bash(context-load) |
/context-load Skill
context-load
You are reloading project context into your conversation. This is typically run after /clear or when context has been lost.
Pre-gathered context
The context-load script has walked from the current working directory upward, collecting all key index files:
!context-load
Instructions
The output above contains the full project context that would normally be loaded at session start. Internalize it now:
- Read and acknowledge the CLAUDE.md file(s) — these contain project guidelines and conventions
- Note the directory tree(s) — understand the current repo structure
- Read CONTEXT.md if present — this tells you what's actively being worked on
- Read MEMORY.md if present — this is the index of accumulated learnings
- Read BESTPRACTICES.md if present — these are cross-project best practices
- Note git status — understand the current state of the working tree
After internalizing, respond with a brief summary:
- Which project(s) you're now oriented to
- Current git status (clean/dirty, branch)
- Any active context entries worth highlighting
If the user passed arguments (e.g., /context-load from a specific directory), those are available as: $ARGUMENTS
Keep the summary concise — the user knows their project, they just need confirmation that you've reloaded context successfully.