context-refresh

To preserve task tracking before clearing context, this Skill captures session identity, open issues, PRs, and task status into a structured handoff document. This written handoff ensures your debugging session resumes cleanly with all prior decisions intact.

You should perform a context refresh when a multi-file investigation feels sluggish or diluted by stale details. The Skill suggests a refresh for long debugging threads to clear noise while preserving key files and behavioral calibration.

Writing a session handoff involves recording session identity, goals, observations, and task status. The Skill guides you through capturing open issue inventories and behavioral calibration so collaborative threads stay aligned after a reset.

A session snapshot for workflow resumption includes session identity, task status, open issues, pull requests, and key files. This structured handoff preserves behavioral calibration and prior decisions to support clean continuation after clearing context.

Yes, you can resume a debugging workflow after the clear command without losing decisions. The Skill preserves active session state and prior observations in a written handoff specifically designed to support clean resumption.

Clearing accumulated context safely requires a session identity to anchor the preserved state. The Skill needs this identity alongside a task snapshot and open issue inventory to ensure your work survives the reset.