How do I install the Claude Restart Compact skill?

Run npx skillmds add majiayu000/claude-restart-compact in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude Restart Compact safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude Restart Compact?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude Restart Compact free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude Restart Compact?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude Restart Compact by majiayu000

Name: Claude Restart Compact
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Claude Restart Compact

Compact context at natural breakpoints to free tokens and continue working. Use PROACTIVELY at phase boundaries, after commits, or when token usage >150k. Better than random auto-compact. Supports custom compaction prompts.

majiayu000 c5e352c 2 files · 2.9 KB Updated Sep 9, 2026 567 repo stars

File contents

Compacting context at natural breakpoint and resuming work...

This will:

Summarize recent conversation to free tokens
Preserve task context and state
Resume with compact history
Continue working on current task

When to Use (Natural Breakpoints)

Use at logical stopping points rather than letting Claude auto-compact randomly:

After completing a phase:

Feature implementation done and committed
Test suite passing
Documentation updated
Natural transition to next phase

At project boundaries:

Completed one component, starting another
Finished refactoring, moving to new feature
After major milestone

Before running out of space:

Token usage >150k (75% of 200k budget)
Long conversations (>100 messages)
Before starting large multi-phase work

Benefits over auto-compact:

Control WHEN compaction happens
Compact at meaningful boundaries
Preserve important context
Custom prompts guide what to keep

Usage

Basic (default compaction):

.claude/skills/claude-restart-resume/scripts/claude-restart.sh compact

With custom prompt (guides what to preserve):

# Set compaction prompt before invoking
export COMPACT_PROMPT="Preserve: API design decisions, database schema, known bugs"
.claude/skills/claude-restart-resume/scripts/claude-restart.sh compact

Compaction Prompts

Custom prompts help preserve important context:

# Keep technical decisions
COMPACT_PROMPT="Preserve architectural decisions and open technical questions"

# Keep project state
COMPACT_PROMPT="Preserve TODO list state, recent commits, and next steps"

# Keep domain knowledge
COMPACT_PROMPT="Preserve domain model, business rules, and API contracts"

The script will pass this to Claude during compaction to guide summarization.

---name: claude-restart-compactdescription: Compact context at natural breakpoints to free tokens and continue working. Use PROACTIVELY at phase boundaries, after commits, or when token usage >150k. Better than random auto-compact. Supports custom compaction prompts.--- Compacting context at natural breakpoint and resuming work... This will: - Summarize recent conversation to free tokens - Preserve task context and state - Resume with compact history - Continue working on current task ## When to Use (Natural Breakpoints) Use at **logical stopping points** rather than letting Claude auto-compact randomly: **After completing a phase:** - Feature implementation done and committed - Test suite passing - Documentation updated - Natural transition to next phase **At project boundaries:** - Completed one component, starting another - Finished refactoring, moving to new feature - After major milestone **Before running out of space:** - Token usage >150k (75% of 200k budget) - Long conversations (>100 messages) - Before starting large multi-phase work **Benefits over auto-compact:** - Control WHEN compaction happens - Compact at meaningful boundaries - Preserve important context - Custom prompts guide what to keep ## Usage **Basic** (default compaction): ```bash .claude/skills/claude-restart-resume/scripts/claude-restart.sh compact ``` **With custom prompt** (guides what to preserve): ```bash # Set compaction prompt before invoking export COMPACT_PROMPT="Preserve: API design decisions, database schema, known bugs" .claude/skills/claude-restart-resume/scripts/claude-restart.sh compact ``` ## Compaction Prompts Custom prompts help preserve important context: ```bash # Keep technical decisions COMPACT_PROMPT="Preserve architectural decisions and open technical questions" # Keep project state COMPACT_PROMPT="Preserve TODO list state, recent commits, and next steps" # Keep domain knowledge COMPACT_PROMPT="Preserve domain model, business rules, and API contracts" ``` The script will pass this to Claude during compaction to guide summarization.

Frequently asked questions