Strategic Context Compaction FAQs

Question 1

How does the skill know when to suggest a compaction?

Accepted Answer

The skill uses a script called suggest-compact.sh that runs on the PreToolUse hook. It counts tool calls and triggers a reminder once you hit a specific threshold, defaultly set to 50 calls.

Question 2

Which tools trigger the compaction suggestion hook?

Accepted Answer

By default, the hook is configured to monitor the 'Edit' and 'Write' tools, as these typically represent significant progress in a development task.

Question 3

Why is strategic compaction better than auto-compaction?

Accepted Answer

Auto-compaction triggers at arbitrary points, often mid-task, which can result in the loss of critical context. Strategic compaction allows you to clear the history at logical breaks, like after a plan is finalized.

Question 4

Does this skill automatically run the /compact command for me?

Accepted Answer

No, it is designed to be a suggestive tool. It provides a reminder and guidance on when to compact, but leaves the final decision to the developer to ensure no active work is interrupted.

Question 5

Can I customize the frequency of the compaction reminders?

Accepted Answer

Yes, you can configure the COMPACT_THRESHOLD environment variable to set how many tool calls should occur before the first suggestion appears.

Strategic Context Compaction

주요 기능

사용 사례

Strategic Context Compaction

주요 기능

사용 사례