context-reset

Reset conversation context between auto-engineer iterations using /compact, /clear, or restart-loop.sh.

5|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dburkart/auto-engineer --skill context-reset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-reset
Source: https://github.com/dburkart/auto-engineer/tree/main/templates/skills/context-reset
Command: npx skills add https://github.com/dburkart/auto-engineer --skill context-reset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents stale or accumulated conversation context from corrupting decisions across auto-engineer iterations, reducing cost and avoiding incorrect carryover of old state.

Core Features & Use Cases

  • Compact end-of-cycle summaries: Uses the built-in /compact behavior to trim tokens while preserving the iteration counter, stop-reason history, and current PR state.
  • Full conversation wipes when needed: Recommends /clear when prior-cycle residue is actively causing incorrect reasoning or hallucinated state.
  • Clean process restarts: Advises using scripts/restart-loop.sh to fully reset the container when token ceilings are hit or when a fresh environment is required (e.g., credentials or updated image).

Quick Start

Use /compact at the end of a healthy auto-engineer cycle, and switch to /clear or scripts/restart-loop.sh only when you confirm context corruption or need a fully clean container restart.

Frequently Asked Questions about context-reset

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

FAQPage Schema
How do I prevent context drift in autonomous agent iterations?

Preventing context drift in autonomous agent iterations requires resetting conversation context between runs. Use /compact to trim tokens while preserving the iteration counter, or /clear to wipe stale residue causing incorrect reasoning.

Why does my auto-engineer loop hallucinate state from previous cycles?

Your auto-engineer loop hallucinates state because accumulated conversation context from prior cycles corrupts decisions. Switch to a full conversation wipe using /clear to remove prior-cycle residue that is actively causing incorrect reasoning or hallucinated state.

What is the best way to manage token overruns in CI loop stability?

The best way to manage token overruns in CI loop stability is executing a clean process restart. Run scripts/restart-loop.sh to fully reset the container when token ceilings are hit or when a fresh environment with updated credentials is required.

When should I use /compact versus /clear for conversation reset?

Use /compact for conversation reset at the end of a healthy auto-engineer cycle to trim tokens while preserving state. Switch to /clear only when you confirm prior-cycle residue is actively causing context corruption or hallucinated state.

Does context reset preserve the iteration counter and PR state?

Context reset using /compact preserves the iteration counter, stop-reason history, and current PR state while trimming tokens. If you use /clear or scripts/restart-loop.sh, the conversation state is fully wiped to eliminate context corruption.