1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| context | The user is referencing previous work. Search wiki, session logs, credentials, and coord for context before asking the user. Use when the user says /context, "continue the previous work", "resume", "what did we do on X", "look up the context for this client/project". |
/context — Previous Work Lookup
Grok skill: This maps to the shared command in .claude/commands/context.md.
Per the harness (and CLAUDE.md "Automatic Context Loading" and "Context Recovery" sections):
- ALWAYS check wiki/ first (clients/, projects/, systems/, patterns/).
- Then session-logs/ (root, projects/, clients/).
- credentials.md (or vault).
- Coord API status, locks, messages, components.
- Project CONTEXT.md files.
When this skill runs:
- Read
.claude/commands/context.mdfor the exact protocol. - Use tools:
read_filefor wiki and log files (GrepAI via MCP or the dedicated grep tool is excellent for semantic search across session logs). - Query coord via
run_terminal_commandwith curl to http://172.16.3.30:8001/api/coord/... - Never ask the user for info that is already in these sources.
This is one of the most important commands for maintaining continuity across sessions and machines. The CLAUDE.md has a detailed trigger table.
See the source command for the full checklist and "Never ask for info in:" rules.