Lintel on GitHub Copilot. Generated from skills/pause/SKILL.md; edit the canonical file, then run
li-copilot init.
- Resource root:
../../.. from this skill's base directory (the Lintel source with bin/,
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/ and data/ folders (and a
<base> that the workflow defines as its own directory) mean
../../../skills/pause/ in the Lintel source, not this generated folder.
${LINTEL_SKILLS_DIR:-skills} means the skills root, ../../../skills. A bin/li-run step
runs in the working repository, so use $LINTEL_SKILLS_DIR/pause/ there.
- Shell steps: run Bash snippets with Bash (Git for Windows'
bash.exe on Windows, never
System32\bash.exe). Save a snippet to a temporary .sh file and run
bash "<resource root>/bin/li-run" <file>; it prepares LINTEL_SOURCE_ROOT, LINTEL_REPO_ROOT
and 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=task
with that custom agent, WebFetch=web_fetch.
- Other Lintel workflows are native skills: invoke
/li-<name> rather than reading their
files. Named roles such as CodeReviewer are custom agents.
Pause
Save the current session's load-bearing state to a checkpoint file so a fresh session can resume cold. Use before context bloat hits productivity, OR when handing off to a teammate, OR when ending a session mid-task.
When to use
- An actually available watcher or host observation suggests checkpointing before a fresh session
- You're ending a multi-day task mid-flight and the next session needs the full picture
- You're handing the session off to a teammate
- Before running
/clean (it offers to call this first)
When NOT to use
- Single short task that doesn't span sessions — save is overkill
- Pure question / lookup tasks — nothing stateful to save
Inputs
No required arguments. The skill reads:
- Current checkpoint branch via
_context_branch from bin/_context.sh, including
the historical HEAD bucket for a detached committed checkout
- SLUG via
_context_repo_slug from bin/_context.sh (native — basename of the repo root; no external binary)
- Recent uncommitted work via
git status -s + git diff --stat HEAD
- Active TODOs (this skill's own TodoWrite state if available, else
.claude/plans/todo.md)
- Last 3 user turns (operator pastes them if not introspectable)
Optional argument: a short label describing the in-flight task, either positional or
--label <name>. Pass the selected value to context_save_path; reject conflicting labels.
The command name changes, not the checkpoint grammar, storage roots or helper API.
Workflow
Resolve slug + branch + timestamp.
Compute the checkpoint path via the mechanical core (bin/_context.sh owns naming + directory creation; checkpoint CONTENT stays LLM-written):
source "${LINTEL_SOURCE_ROOT:?Set the trusted Lintel source root}/bin/_context.sh"
path=$(context_save_path "${label:-}") || exit 1
context_save_path reserves an empty file at .claude/runtime/sessions/<branch>/<YYYYMMDD-HHMMSS>-r<repository-key>-<slug>[-<label>]-context-save.md and creates the directory. It refuses unsafe directories and chooses a collision suffix instead of overwriting. The key identifies the canonical repository path, including the shared legacy directory. Keep the -context-save.md suffix: it is persisted data shared by discovery, resume and warming, not a retired command. Empty reservations are not discoverable checkpoints.
Gather:
- What the task is — one-line description (operator-provided or inferred from recent turns).
- What got done — bulleted from todo-list completed items + recent commit messages on this branch.
- What's in-flight — active todo items + dirty git tree summary.
- What's next — top 1-3 next steps.
- Decisions taken — surface any ask_user answers from the session (operator-noted).
- Failed attempts — patterns/approaches tried that didn't work (so next session doesn't re-try).
- Files touched —
git diff --name-only HEAD + any uncommitted-but-staged files.
- Bounded restart sources — explicit relative paths for the next step, not every file
mentioned in the conversation. Use
context_select to preview their actual sizes and
missing/excluded files. Preserve any already-selected work/spec/task artifact references;
do not guess a different initiative or create a second task source.
Write the checkpoint content to $path with this structure:
# Checkpoint — <one-line task description>
**Slug:** <slug>
**Repository:** <canonical absolute repository root from _context_repo_identity>
**Branch:** <branch>
**Timestamp:** <ISO 8601>
**Last commit:** <sha> — <message>
## Task
<2-3 sentences on what's being done and why>
## Done
- [x] item 1
- [x] item 2
## In flight
- [ ] item 3 — <current state, what's blocking>
- [ ] item 4
## Next
1. <very specific next step>
2. <step 2>
3. <step 3>
## Decisions taken
- D1: <decision> — <one-line rationale>
- D2: ...
## Failed attempts
- <approach tried> — <why it didn't work>
## Files touched
- file1.ts
- file2.md
## Resume command
To read this checkpoint in a fresh session: `/li-resume --from <checkpoint-path>`.
Keep the selected work map, original task IDs and verified profile reference unchanged.
- Confirm the write succeeded and is nonempty, then run
context_checkpoint "$path" to
verify the owned read path and show its size/digest. Only then report a saved checkpoint.
This reads metadata; the checkpoint content remains agent-written and must also be reviewed.
Print the exact path so the operator can resume it.
Report format
✓ Checkpoint saved
Path: <full path>
Size: <bytes>
Resume: /li-resume --from <path>
Edge cases
- No git repo: still save using the installed Git hashing tool, with branch
no-branch.
Slug derives from the explicit root/cwd basename. An unborn Git branch retains its actual name.
- No
.claude/runtime/sessions/<branch>/: context_save_path creates it.
- Existing checkpoint with same timestamp: reserve a
-copyNNNN suffix. Never overwrite.
- Long Windows paths: the shared helper checks ancestry and reserves/reads through a
same-location native I/O spelling, while returning the unchanged logical checkpoint
path. It does not shorten repository keys, labels or roots, or alter OS/global Git settings.
- Operator pastes recent turns inline: capture them verbatim under a
## Recent turns (operator-pasted) section.
Compliance integration
This skill writes a checkpoint outside the committed tree (to the gitignored .claude/runtime/sessions/). Per Lintel Layer 2:
- The checkpoint file may contain references to in-flight work that touched files in the repo. Operator confirms NO customer-data is captured in the checkpoint before saving.
- Default sanity-grep before write: if the checkpoint text matches secret-shaped patterns, halt and surface to operator.
Failure modes
- Write fails (disk full / permission denied): report failure and preserve any local draft;
do not claim success or dump possibly sensitive checkpoint content to another surface.
- Slug resolution fails: fall back to
unknown-project.
- No Git branch:
no-branch placeholder; a detached committed checkout uses HEAD.
A missing Git/Python tool or invalid directory is an explicit failure, not a saved checkpoint.
Examples
The repository key below is synthetic. Use the exact path returned by
context_save_path; do not guess a key or reuse another repository's example.
Mid-task save with label:
> /li-pause phase-2-skills-batch-1
✓ Checkpoint saved
Path: .claude/runtime/sessions/main/20260527-153022-r0123456789abcdef0123456789abcdef01234567-lintel-phase-2-skills-batch-1-context-save.md
Resume: /li-resume --from .claude/runtime/sessions/main/20260527-153022-r0123456789abcdef0123456789abcdef01234567-lintel-phase-2-skills-batch-1-context-save.md
No label:
> /li-pause
✓ Checkpoint saved
Path: .claude/runtime/sessions/main/20260527-153455-r0123456789abcdef0123456789abcdef01234567-lintel-context-save.md
See also
/li-resume --from <path> — read an owned checkpoint into a fresh session
/li-resume — discovers checkpoints through context_latest without letting local
history override an explicitly selected work map or committed active work
/clean — manual self-maintenance trigger (offers to call this first)
- An actually configured host warning or an explicit
/li-context-budget observation
may suggest this skill; no registered watcher or automatic invocation is implied
This saves continuity notes, not a backup of source bytes or a change to the host's active
context. Owned file rollback uses bin/li-snapshot.py through /li-safe-install; never
confuse it with reading a Markdown checkpoint. Hook references above apply only when that
host integration was actually configured and observed.
1---2name: li-pause3description: Use before the context window fills up or before clearing the session to save the current state to a checkpoint file. Reach for it when a session is getting heavy and you want to preserve where you are so a later session can pick up exactly here.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-pause6---78> **Lintel on GitHub Copilot.** Generated from `skills/pause/SKILL.md`; edit the canonical file, then run9> `li-copilot init`.10> - **Resource root:** `../../..` from this skill's base directory (the Lintel source with `bin/`,11> `lib/`, `skills/`). Write plans, state and evidence into the working repository's `.claude/`12> tree, never into the resource root.13> - **Skill-relative paths:** this skill's own `scripts/`, `references/` and `data/` folders (and a14> `<base>` that the workflow defines as its own directory) mean15> `../../../skills/pause/` in the Lintel source, not this generated folder.16> `${LINTEL_SKILLS_DIR:-skills}` means the skills root, `../../../skills`. A `bin/li-run` step17> runs in the working repository, so use `$LINTEL_SKILLS_DIR/pause/` there.18> - **Shell steps:** run Bash snippets with Bash (Git for Windows' `bash.exe` on Windows, never19> `System32\bash.exe`). Save a snippet to a temporary `.sh` file and run20> `bash "<resource root>/bin/li-run" <file>`; it prepares `LINTEL_SOURCE_ROOT`, `LINTEL_REPO_ROOT`21> and the profile context.22> - **Tools:** Read=`view`, Write=`create`, Edit=`edit`, Bash=`bash`/`powershell`, Grep=`grep`,23> Glob=`glob`, AskUserQuestion=`ask_user`, TodoWrite=the plan checklist, Task or a named role=`task`24> with that custom agent, WebFetch=`web_fetch`.25> - **Other Lintel workflows** are native skills: invoke `/li-<name>` rather than reading their26> files. Named roles such as `CodeReviewer` are custom agents.2728# Pause2930Save the current session's load-bearing state to a checkpoint file so a fresh session can resume cold. Use **before** context bloat hits productivity, OR when handing off to a teammate, OR when ending a session mid-task.3132## When to use3334- An actually available watcher or host observation suggests checkpointing before a fresh session35- You're ending a multi-day task mid-flight and the next session needs the full picture36- You're handing the session off to a teammate37- Before running `/clean` (it offers to call this first)3839## When NOT to use4041- Single short task that doesn't span sessions — save is overkill42- Pure question / lookup tasks — nothing stateful to save4344## Inputs4546- **No required arguments.** The skill reads:47 - Current checkpoint branch via `_context_branch` from `bin/_context.sh`, including48 the historical `HEAD` bucket for a detached committed checkout49 - SLUG via `_context_repo_slug` from `bin/_context.sh` (native — basename of the repo root; no external binary)50 - Recent uncommitted work via `git status -s` + `git diff --stat HEAD`51 - Active TODOs (this skill's own TodoWrite state if available, else `.claude/plans/todo.md`)52 - Last 3 user turns (operator pastes them if not introspectable)5354- **Optional argument:** a short label describing the in-flight task, either positional or55 `--label <name>`. Pass the selected value to `context_save_path`; reject conflicting labels.56 The command name changes, not the checkpoint grammar, storage roots or helper API.5758## Workflow59601. Resolve slug + branch + timestamp.612. Compute the checkpoint path via the mechanical core (`bin/_context.sh` owns naming + directory creation; checkpoint CONTENT stays LLM-written):6263 ```bash64 source "${LINTEL_SOURCE_ROOT:?Set the trusted Lintel source root}/bin/_context.sh"65 path=$(context_save_path "${label:-}") || exit 166 ```6768 `context_save_path` reserves an empty file at `.claude/runtime/sessions/<branch>/<YYYYMMDD-HHMMSS>-r<repository-key>-<slug>[-<label>]-context-save.md` and creates the directory. It refuses unsafe directories and chooses a collision suffix instead of overwriting. The key identifies the canonical repository path, including the shared legacy directory. Keep the `-context-save.md` suffix: it is persisted data shared by discovery, resume and warming, not a retired command. Empty reservations are not discoverable checkpoints.693. Gather:70 - **What the task is** — one-line description (operator-provided or inferred from recent turns).71 - **What got done** — bulleted from todo-list completed items + recent commit messages on this branch.72 - **What's in-flight** — active todo items + dirty git tree summary.73 - **What's next** — top 1-3 next steps.74 - **Decisions taken** — surface any ask_user answers from the session (operator-noted).75 - **Failed attempts** — patterns/approaches tried that didn't work (so next session doesn't re-try).76 - **Files touched** — `git diff --name-only HEAD` + any uncommitted-but-staged files.77 - **Bounded restart sources** — explicit relative paths for the next step, not every file78 mentioned in the conversation. Use `context_select` to preview their actual sizes and79 missing/excluded files. Preserve any already-selected work/spec/task artifact references;80 do not guess a different initiative or create a second task source.814. Write the checkpoint content to `$path` with this structure:8283```markdown84# Checkpoint — <one-line task description>8586**Slug:** <slug>87**Repository:** <canonical absolute repository root from _context_repo_identity>88**Branch:** <branch>89**Timestamp:** <ISO 8601>90**Last commit:** <sha> — <message>9192## Task9394<2-3 sentences on what's being done and why>9596## Done9798- [x] item 199- [x] item 2100101## In flight102103- [ ] item 3 — <current state, what's blocking>104- [ ] item 4105106## Next1071081. <very specific next step>1092. <step 2>1103. <step 3>111112## Decisions taken113114- D1: <decision> — <one-line rationale>115- D2: ...116117## Failed attempts118119- <approach tried> — <why it didn't work>120121## Files touched122123- file1.ts124- file2.md125126## Resume command127128To read this checkpoint in a fresh session: `/li-resume --from <checkpoint-path>`.129Keep the selected work map, original task IDs and verified profile reference unchanged.130```1311325. Confirm the write succeeded and is nonempty, then run `context_checkpoint "$path"` to133 verify the owned read path and show its size/digest. Only then report a saved checkpoint.134 This reads metadata; the checkpoint content remains agent-written and must also be reviewed.135 Print the exact path so the operator can resume it.136137## Report format138139```140✓ Checkpoint saved141 Path: <full path>142 Size: <bytes>143 Resume: /li-resume --from <path>144```145146## Edge cases147148- **No git repo:** still save using the installed Git hashing tool, with branch `no-branch`.149 Slug derives from the explicit root/cwd basename. An unborn Git branch retains its actual name.150- **No `.claude/runtime/sessions/<branch>/`:** `context_save_path` creates it.151- **Existing checkpoint with same timestamp:** reserve a `-copyNNNN` suffix. Never overwrite.152- **Long Windows paths:** the shared helper checks ancestry and reserves/reads through a153 same-location native I/O spelling, while returning the unchanged logical checkpoint154 path. It does not shorten repository keys, labels or roots, or alter OS/global Git settings.155- **Operator pastes recent turns inline:** capture them verbatim under a `## Recent turns (operator-pasted)` section.156157## Compliance integration158159This skill writes a checkpoint outside the committed tree (to the gitignored `.claude/runtime/sessions/`). Per Lintel Layer 2:160- The checkpoint file may contain references to in-flight work that touched files in the repo. Operator confirms NO customer-data is captured in the checkpoint before saving.161- Default sanity-grep before write: if the checkpoint text matches secret-shaped patterns, halt and surface to operator.162163## Failure modes164165- **Write fails (disk full / permission denied):** report failure and preserve any local draft;166 do not claim success or dump possibly sensitive checkpoint content to another surface.167- **Slug resolution fails:** fall back to `unknown-project`.168- **No Git branch:** `no-branch` placeholder; a detached committed checkout uses `HEAD`.169 A missing Git/Python tool or invalid directory is an explicit failure, not a saved checkpoint.170171## Examples172173The repository key below is synthetic. Use the exact path returned by174`context_save_path`; do not guess a key or reuse another repository's example.175176**Mid-task save with label:**177```178> /li-pause phase-2-skills-batch-1179✓ Checkpoint saved180 Path: .claude/runtime/sessions/main/20260527-153022-r0123456789abcdef0123456789abcdef01234567-lintel-phase-2-skills-batch-1-context-save.md181 Resume: /li-resume --from .claude/runtime/sessions/main/20260527-153022-r0123456789abcdef0123456789abcdef01234567-lintel-phase-2-skills-batch-1-context-save.md182```183184**No label:**185```186> /li-pause187✓ Checkpoint saved188 Path: .claude/runtime/sessions/main/20260527-153455-r0123456789abcdef0123456789abcdef01234567-lintel-context-save.md189```190191## See also192193- `/li-resume --from <path>` — read an owned checkpoint into a fresh session194- `/li-resume` — discovers checkpoints through `context_latest` without letting local195 history override an explicitly selected work map or committed active work196- `/clean` — manual self-maintenance trigger (offers to call this first)197- An actually configured host warning or an explicit `/li-context-budget` observation198 may suggest this skill; no registered watcher or automatic invocation is implied199200This saves continuity notes, not a backup of source bytes or a change to the host's active201context. Owned file rollback uses `bin/li-snapshot.py` through `/li-safe-install`; never202confuse it with reading a Markdown checkpoint. Hook references above apply only when that203host integration was actually configured and observed.