Strategic Context Compactor FAQs

Question 1

Why should I use manual compaction over auto-compaction?

Accepted Answer

Auto-compaction often triggers at arbitrary points, potentially losing vital context in the middle of a complex task. Strategic compaction ensures you only refresh context when you have reached a logical stopping point.

Question 2

How does this skill track my usage progress?

Accepted Answer

It uses a PreToolUse hook to count successful Edit and Write tool calls. Once a configurable threshold (default 50) is reached, it suggests a manual /compact command.

Question 3

Does this skill work automatically with all Claude Code tools?

Accepted Answer

The skill is specifically configured to monitor Edit and Write operations, which are the primary indicators of task progress and context accumulation in a development workflow.

Question 4

Will compacting my context delete my progress?

Accepted Answer

No, the /compact command summarizes the conversation history to save tokens. It does not affect your local files or the actual code you have written.

Question 5

Can I customize the frequency of the compaction suggestions?

Accepted Answer

Yes, you can modify the COMPACT_THRESHOLD environment variable to adjust the number of tool calls required before the first suggestion appears.

Strategic Context Compactor

主要功能

使用场景

Strategic Context Compactor

主要功能

使用场景