recover-from-lost-shell-session

Use when a shell session disappears mid-command or reports 'No active session found'. Follow systematic recovery steps before reissuing commands.

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/TingxiaoDong/FeishuCLassmate --skill recover-from-lost-shell-session

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	recover-from-lost-shell-session
description	Use when a shell session disappears mid-command or reports 'No active session found'. Follow systematic recovery steps before reissuing commands.
category	automation

On "No active session found" or session loss, check what was accomplished before the loss.
Parse any partial output that was returned before session died.
If session lost mid-command, restart with --dry-run to verify syntax first.
Before running npm/node commands that failed, verify:
- node_modules/ exists: ls node_modules/ | head -5
- Package installed: npm list <package-name>
- Correct working directory: pwd
If the original command failed with MODULE_NOT_FOUND, check package.json dependencies before re-running.

Anti-pattern: Immediately re-running the same command that failed without diagnosing why the session was lost.

name	recover-from-lost-shell-session
description	Use when a shell session disappears mid-command or reports 'No active session found'. Follow systematic recovery steps before reissuing commands.
category	automation

On "No active session found" or session loss, check what was accomplished before the loss.
Parse any partial output that was returned before session died.
If session lost mid-command, restart with --dry-run to verify syntax first.
Before running npm/node commands that failed, verify:
- node_modules/ exists: ls node_modules/ | head -5
- Package installed: npm list <package-name>
- Correct working directory: pwd
If the original command failed with MODULE_NOT_FOUND, check package.json dependencies before re-running.

Anti-pattern: Immediately re-running the same command that failed without diagnosing why the session was lost.