Lintel on GitHub Copilot. Generated from skills/fix/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/fix/ 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/fix/ 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.
You are the FIX composite shortcut — hotfix mode pre-baked. Not nestable — /li-fix is itself the hop-in shortcut.
When to use
- Known bug + path to fix is clear
- No design discussion needed (e.g., "null pointer at line 47, add null check")
- Production incident requiring fast ship
- Operator already understands root cause
- Cost expectation: ~5-15k tokens, 10-30 min
When NOT to use
- New feature work — use
/li-cycle (full)
- Unclear root cause — use
/li-diagnose first, then /li-fix
- Customer-deliverable involved — use
/li-cycle --mode customer-engagement (the active pack's voice + compliance gates apply)
- Significant architecture change — needs DEFINE + PLAN phases
Workflow
Step 1 — Pre-flight
Confirm hotfix mode is appropriate:
- Reuse the supplied diagnosis and authority. Ask through the actual host channel
only if the root cause, intended behavior or mutation scope is unresolved.
- If the diagnosis is missing, use
/li-diagnose; do not improvise a fix from
a review/research request.
Keep BUILD's work contract even though the full PLAN ceremony is skipped. Use the
selected work map and bin/li-work-artifacts.py.
An existing defect task keeps its original ID. For a new bounded authorized fix,
record a minimal native spec/plan/prompt/work.json with the reproduction, intended
behavior, owned files, one stable leaf, regression check and existing scope approval.
The map's tasks points to that plan; no extra backlog or unrelated interview.
If required planning/review is missing, the alias remains incomplete.
For selected Spec Kit defect work, use
selected external authority before
that native-new-fix fallback. Retain the original bug assessment/test evidence
and existing tasks.md, including converge-appended IDs; add a newly authorized
defect task only through that original task owner. Do not create a parallel
native bug plan or run a second fix owner, workflow gate or enabled hook over
the same scope. A verified bug report does not itself approve repair or SHIP.
Step 2 — Delegate to /li-cycle
/li-cycle --mode hotfix --from SENSE --to SHIP --skip DEFINE,DISCOVER,PLAN,CAPTURE
Mode preset handles:
- audience=solo
- voice_tier=internal
- compliance=minimal (HARD-RULES still enforced per the pack's compliance mode; default advisory)
- Same verified P07 profile/required-policy reference and original task selection
- Cost expectation pre-set low
Step 3 — Post-fix
After SHIP DONE, surface:
HOTFIX SHIPPED — <commit/PR>
Skipped phases:
- DEFINE (no design needed for known fix)
- DISCOVER (no codebase mapping needed)
- Full PLAN ceremony (minimal approved mapped work and acceptance were retained)
- CAPTURE (no durable artifacts to capture)
If this fix reveals a pattern worth capturing (lesson for /li-lessons-promote),
run /li-capture manually now.
This is a soft prompt — operator decides if CAPTURE is worth running post-hoc.
Integration
Delegates to /li-cycle --mode hotfix. No new behavior beyond that.
Anti-patterns
- Using /li-fix for new feature work — bypass DEFINE/PLAN = guaranteed scope drift
- Skipping CAPTURE when fix reveals durable lesson — soft-prompted post-hoc, don't ignore
1---2name: li-fix3description: Use for a known bug with a clear fix path that needs to ship now — runs the abbreviated SENSE, BUILD, REVIEW, SHIP path and skips design, discovery, and planning. The hotfix shortcut; reach for it when the diagnosis is already done and only the fix remains.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-fix6---78> **Lintel on GitHub Copilot.** Generated from `skills/fix/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/fix/` 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/fix/` 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.2728You are the FIX composite shortcut — hotfix mode pre-baked. Not nestable — /li-fix is itself the hop-in shortcut.2930## When to use3132- Known bug + path to fix is clear33- No design discussion needed (e.g., "null pointer at line 47, add null check")34- Production incident requiring fast ship35- Operator already understands root cause36- Cost expectation: ~5-15k tokens, 10-30 min3738## When NOT to use3940- New feature work — use `/li-cycle` (full)41- Unclear root cause — use `/li-diagnose` first, then `/li-fix`42- Customer-deliverable involved — use `/li-cycle --mode customer-engagement` (the active pack's voice + compliance gates apply)43- Significant architecture change — needs DEFINE + PLAN phases4445## Workflow4647### Step 1 — Pre-flight4849Confirm hotfix mode is appropriate:50- Reuse the supplied diagnosis and authority. Ask through the actual host channel51 only if the root cause, intended behavior or mutation scope is unresolved.52- If the diagnosis is missing, use `/li-diagnose`; do not improvise a fix from53 a review/research request.5455Keep BUILD's work contract even though the full PLAN ceremony is skipped. Use the56[selected work map](../../../skills/spec-kit/references/work-map.md) and `bin/li-work-artifacts.py`.57An existing defect task keeps its original ID. For a new bounded authorized fix,58record a minimal native spec/plan/prompt/work.json with the reproduction, intended59behavior, owned files, one stable leaf, regression check and existing scope approval.60The map's tasks points to that plan; no extra backlog or unrelated interview.61If required planning/review is missing, the alias remains incomplete.6263For selected Spec Kit defect work, use64[selected external authority](../../../skills/spec-kit/references/selected-authority.md) before65that native-new-fix fallback. Retain the original bug assessment/test evidence66and existing tasks.md, including converge-appended IDs; add a newly authorized67defect task only through that original task owner. Do not create a parallel68native bug plan or run a second fix owner, workflow gate or enabled hook over69the same scope. A verified bug report does not itself approve repair or SHIP.7071### Step 2 — Delegate to /li-cycle7273```bash74/li-cycle --mode hotfix --from SENSE --to SHIP --skip DEFINE,DISCOVER,PLAN,CAPTURE75```7677Mode preset handles:78- audience=solo79- voice_tier=internal80- compliance=minimal (HARD-RULES still enforced per the pack's compliance mode; default advisory)81- Same verified P07 profile/required-policy reference and original task selection82- Cost expectation pre-set low8384### Step 3 — Post-fix8586After SHIP DONE, surface:87```88HOTFIX SHIPPED — <commit/PR>8990Skipped phases:91 - DEFINE (no design needed for known fix)92 - DISCOVER (no codebase mapping needed)93 - Full PLAN ceremony (minimal approved mapped work and acceptance were retained)94 - CAPTURE (no durable artifacts to capture)9596If this fix reveals a pattern worth capturing (lesson for /li-lessons-promote),97run /li-capture manually now.98```99100This is a soft prompt — operator decides if CAPTURE is worth running post-hoc.101102## Integration103104Delegates to `/li-cycle --mode hotfix`. No new behavior beyond that.105106## Anti-patterns107108- **Using /li-fix for new feature work** — bypass DEFINE/PLAN = guaranteed scope drift109- **Skipping CAPTURE when fix reveals durable lesson** — soft-prompted post-hoc, don't ignore