void-context

Manages agent context windows through clearing, compaction, and subagent delegation.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-context-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-context
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-context
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-context-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long agent sessions silently degrade as the context window fills with stale file dumps, abandoned approaches, and failed corrections, causing the model to drop earlier constraints without any error. This Skill provides a discipline for treating context as a managed budget so quality does not rot invisibly across turns. ## Core Features & Use Cases - Four context moves: Clear between unrelated tasks, reset after two failed corrections, compact long coherent threads with a named focus, and delegate heavy multi-file investigation to fresh-context subagents that return only conclusions. - Anti-context-rot persistence: Routes durable state (plans, checkpoints, ADRs, provider state) to the filesystem so work survives any session reset. - Signal-driven action table: Maps symptoms like forgotten constraints, correction loops, and widening searches to the correct remediation move. - Use Case: During a long debugging session the agent starts re-asking settled questions and contradicting earlier decisions; apply the two-correction reset, compact with a focus, and push further log reading into a subagent to restore reasoning quality. ## Quick Start Ask the agent to review the current session for context-rot signals and apply the appropriate clear, compact, or subagent delegation move before continuing the task.

Frequently Asked Questions about void-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent context rot in long Claude Code sessions?

Treat context as a budget: run /clear between unrelated tasks, use /compact with a named focus for long coherent work, and keep durable state on disk. Aim to keep effective usage around 40-60% rather than filling the window.

When should I use /clear versus /compact?

Use /clear when the next task is unrelated to the current one, since leftover context only competes for attention. Use /compact <focus> when the subject is the same but the history is heavy, naming the focus so the summary keeps the relevant thread.

How do subagents help with context window management?

Subagents investigate with their own fresh context and return only a compacted structured summary with findings and file:line pointers. This keeps twenty read files out of your main window when you only needed two sentences of conclusion.

What should I do when corrections keep failing in an agent session?

Stop after two failed corrections instead of stacking a third. Run /clear, then re-prompt from scratch with a single reformulated statement that folds in what the failures taught you, since a clean window beats a confused one.

Does clearing the context window lose my work?

Clearing only loses semantic residue that lived solely in the chat. Persist plans, checkpoints, decisions, and provider state to disk first, then /clear has a durable recovery point and the next session can resume from files alone.