# Stuck Session Diagnosis

> Use when another Claude Code session appears frozen, stuck, or abnormally slow and needs process-level diagnosis and reporting.

- Skill: `wimi321/stuck-session-diagnosis` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add wimi321/stuck-session-diagnosis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/wimi321/stuck-session-diagnosis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: wimi321 (https://skillmd.com/u/wimi321)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/wimi321/stuck-session-diagnosis

---



# Stuck Session Diagnosis

Use this skill to investigate slow or frozen local agent sessions.

## Workflow
1. List candidate agent processes.
2. Check CPU, RSS, state, uptime, and child processes.
3. Sample suspicious processes again to confirm sustained issues.
4. Inspect related debug logs when possible.
5. Produce a concise diagnosis and escalation-ready report.

## Guardrails
- Diagnostic only: do not kill or signal processes unless asked.
- Confirm suspicious metrics are sustained, not transient.
- Keep the final report focused on actionable symptoms.

## Example Requests
- Find out why another Claude session on this machine is frozen.
- Inspect local agent processes and tell me if one is hung.

## Inputs
- Observed symptom
- Process state
- Optional target PID

## Outputs
- Diagnosis summary
- Evidence from process inspection
- Escalation-ready report

## Success Criteria
- Suspicious sessions were confirmed rather than guessed.
- Supporting process data was captured.
- The report is concise and actionable.

## Non-Goals
- Killing processes by default
- Reporting transient blips as confirmed hangs

## Source Provenance
Derived from `src/skills/bundled/stuck.ts`.