Lintel on GitHub Copilot. Generated from skills/pack-switch/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/pack-switch/ 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/pack-switch/ 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.
Pack switch
This entry owns the shared pack lifecycle.
Follow its validation, authorization, real helper invocation, full returned
reference and interruption/recovery procedure. An explicit switch request already
authorizes its stated scope; ask only for missing decisions.
The existing pack-list, pack-validate, pack-create and pack-switch names
remain. Read-only discovery/validation never implies mutation. A switch changes
the selected policy context; it does not install plugins, activate hooks, grant
host permission or select models. Required-policy errors stay blocked.
1---2name: li-pack-switch3description: Use to explicitly switch the effective pack through the structured profile lifecycle, preserving required policy, configured paths and generation-bound recovery.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-pack-switch6---78> **Lintel on GitHub Copilot.** Generated from `skills/pack-switch/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/pack-switch/` 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/pack-switch/` 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# Pack switch2930This entry owns the [shared pack lifecycle](../../../skills/pack-switch/references/lifecycle.md#switch).31Follow its validation, authorization, real helper invocation, full returned32reference and interruption/recovery procedure. An explicit switch request already33authorizes its stated scope; ask only for missing decisions.3435The existing `pack-list`, `pack-validate`, `pack-create` and `pack-switch` names36remain. Read-only discovery/validation never implies mutation. A switch changes37the selected policy context; it does not install plugins, activate hooks, grant38host permission or select models. Required-policy errors stay blocked.