Lintel on GitHub Copilot. Generated from
skills/clean/SKILL.md; edit the canonical file, then runli-copilot init.
- Resource root:
../../..from this skill's base directory (the Lintel source withbin/,lib/,skills/). Write plans, state and evidence into the working repository's.claude/tree, never into the resource root.- Skill-relative paths: this skill's own
scripts/,references/anddata/folders (and a<base>that the workflow defines as its own directory) mean../../../skills/clean/in the Lintel source, not this generated folder.${LINTEL_SKILLS_DIR:-skills}means the skills root,../../../skills. Abin/li-runstep runs in the working repository, so use$LINTEL_SKILLS_DIR/clean/there.- Shell steps: run Bash snippets with Bash (Git for Windows'
bash.exeon Windows, neverSystem32\bash.exe). Save a snippet to a temporary.shfile and runbash "<resource root>/bin/li-run" <file>; it preparesLINTEL_SOURCE_ROOT,LINTEL_REPO_ROOTand the profile context.- Tools: Read=
view, Write=create, Edit=edit, Bash=bash/powershell, Grep=grep, Glob=glob, AskUserQuestion=ask_user, TodoWrite=the plan checklist, Task or a named role=taskwith that custom agent, WebFetch=web_fetch.- Other Lintel workflows are native skills: invoke
/li-<name>rather than reading their files. Named roles such asCodeReviewerare custom agents.
/clean
Manual companion to optional context-bloat watchers. When a session feels heavy, show
the available observations and the continuity path: /li-pause, a fresh session, then
/li-resume --from <checkpoint>. Nothing is compacted or deleted automatically.
Lintel cannot expand or erase a host's active model context. This is a compatibility entry into shared context-budget/checkpoint guidance, not a second context policy or compaction engine.
When to use
- A watcher hook fired and surfaced "consider /clean"
- You FEEL the session got heavy — output quality dropped, you're repeating context, tool-call rate accelerated, agent forgets earlier decisions
- Before stepping away for >2 hours (so resume is clean)
- After a long DEFINE, PLAN and BUILD sequence consumed substantial context
When NOT to use
- Pure short Q&A — nothing to clean
- Mid-tool-call sequences — let the current sequence finish first
- Before a
/ship— let ship complete, THEN clean
Inputs
- No required arguments. Skill computes:
- Estimated token count (best-effort — count tool-result sizes + recent turn lengths)
- Tool-call count for this session
- Skills invoked this session
- Whether a checkpoint exists for current slug + branch (and how recent)
Workflow
- Read available session weight signals through
/li-context-budget:- P03
context_budgetcarries observed/estimated usage and its source, or unknown - Tool-call count
- Skills invoked count
- Time elapsed since session start
- P03
- Read recent checkpoint:
source "${LINTEL_SOURCE_ROOT:?select trusted source}/bin/_context.sh"; context_latest(checkpoints live at.claude/runtime/sessions/<branch>/)- If exists: timestamp, age in minutes
- Optional watcher advice: inspect only explicitly configured and authorized thresholds. They are advisory warning points, not host capacity or proof that a watcher is installed/running. Do not create another threshold store here.
- Decision tree:
- If relevant signals are unknown, report unknown; absent telemetry is not green.
- Supplied observations below configured advice thresholds do not certify session health.
- If session is ABOVE warn threshold(s): recommend
/li-pause+ restart. - Reuse a checkpoint only after verifying its selected work/profile and contents, not simply because it is younger than five minutes.
- Print readout + offer next step.
Report format
Illustrative observed signals (not an actual run):
Session observations: within configured advisory thresholds; host headroom still requires evidence
Estimated tokens: ~24,000 (warn at 50,000)
Tool calls: 42 (warn at 80)
Skills invoked: define, inspect
Time elapsed: 1h 47m
Latest checkpoint: 2h ago (.claude/runtime/sessions/main/20260527-...-context-save.md)
No cleanup needed yet. Run /clean again if session grows heavier.
Illustrative warning:
Session observations: over a configured advisory warning
Estimated tokens: ~62,000 (warn at 50,000 — exceeded)
Tool calls: 73 (warn at 80 — close)
Skills invoked: define, inspect, build, clean
Time elapsed: 3h 12m
Latest checkpoint: 45m ago
Recommended:
1. /li-pause phase-2-batch-1 (write a checkpoint)
2. Close this session
3. Open a fresh session in the actual host, restore the owned checkpoint
This is a soft warning. You can keep going if you have <30 min of focused work left.
Red (over escalation, or both watchers tripped):
Session health: ✗ context bloat likely
Estimated tokens: ~85,000 (escalation at 80,000 — exceeded)
Tool calls: 142 (escalation at 130 — exceeded)
Skills invoked: [list]
Time elapsed: 5h 22m
STRONG recommendation:
1. /li-pause (before more work adds context)
2. Close session
3. Fresh session → /li-resume --from <checkpoint>
If you push past this, expect:
- Slower tool calls
- Forgotten decisions from earlier in the session
- Repeated context summaries (wasted tokens)
Edge cases
- No configured watcher thresholds: use shared context advice; do not invent a 1M window or a new default warning policy.
- No checkpoint history: skip the "latest checkpoint" line.
- Operator overrides default thresholds: read them from config and apply.
- Token/tool counts unavailable: explicitly report unknown, not zero or healthy.
Honest framing
Only a real supported host operation can compact a conversation. This skill:
- Surfaces the right thresholds
- Suggests
/li-pause+ restart +/li-resume --from <checkpoint> - Doesn't perform any auto-action — operator owns the call
- Keeps selected-map/P07 references in the checkpoint through the shared lifecycle. Disk archiving and future read exclusions cannot reclaim already-sent context.
These are optional observations and manual continuity steps, not a background maintenance engine.
Failure modes
- Token count estimation off: report it's an estimate, not authoritative.
context_latestreturns nothing (no.claude/runtime/sessions/<branch>/checkpoints): treat as no-checkpoint-history.- Operator runs /clean during a sub-skill chain: report current state but warn that the chain hasn't completed yet — clean AFTER chain finishes.
Examples
Healthy session:
> /clean
Session health: ✓ within thresholds
...
No cleanup needed yet.
Bloated session:
> /clean
Session health: ✗ context bloat likely
...
Recommendation: /li-pause, then resume the owned checkpoint in a fresh session.
See also
/li-pause— paired write step/li-resume --from <checkpoint>— paired read step- Optional watcher hooks — registration and observation must be separately verified
~/.lintel/config.yaml— threshold overrides