Show current context status and session health. Use to check how much context has been used, whether auto-compact is approaching, and what state will be preserved.
Install
npx skillscat add pedrohcgs/claude-code-my-workflow/context-status Install via the SkillsCat registry.
About this skill
This skill displays the current context usage percentage, active plan status, and preservation state for a Claude Code session. It helps determine when auto-compact is approaching and what state will be preserved during compaction. Developers should use it to monitor session health and plan for context management before reaching limits.
SKILL.md
/context-status — Check Session Health
Show the current session status including context usage estimate, active plan,
and preservation state.
What This Skill Shows
- Context usage estimate — Approximate % of context window used
- Active plan — Current plan file and status
- Session log — Most recent session log
- Preservation state — What will survive compaction
Workflow
Step 1: Check Context Monitor Cache
Read the context monitor cache to get the current estimate:
cat ~/.claude/sessions/*/context-monitor-cache.json 2>/dev/null | head -20Step 2: Find Active Plan
ls -lt quality_reports/plans/*.md 2>/dev/null | head -3Step 3: Find Session Log
ls -lt quality_reports/session_logs/*.md 2>/dev/null | head -1Step 4: Report Status
Format the output:
📊 Session Status
─────────────────────────────────
Context Usage: ~XX% (estimated)
Auto-compact: [approaching | not imminent]
📋 Active Plan
File: quality_reports/plans/YYYY-MM-DD_description.md
Status: [draft | approved | in_progress | completed]
Task: [current unchecked task or "none"]
📝 Session Log
File: quality_reports/session_logs/YYYY-MM-DD_description.md
✓ Preservation Check
• Pre-compact hook: [configured | missing]
• Post-compact restore: [configured | missing]
• Session state will be saved before compactionNotes
- Context % is an estimate based on tool call count
- Actual compaction is triggered by Claude Code automatically
- All important state is saved to disk (plans, logs, MEMORY.md)