Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From claudestrophobic
Lists, deletes, and prunes sessions in the current project. Useful for cleaning up old sessions or deleting a specific session by UUID.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudestrophobic:sessions [list | delete <name|uuid> | prune --older <duration> | browse][list | delete <name|uuid> | prune --older <duration> | browse]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run: `python3 "${CLAUDE_PLUGIN_ROOT}/cli/cc.py" sessions "${CLAUDE_PROJECT_DIR}" <command>`
Run: python3 "${CLAUDE_PLUGIN_ROOT}/cli/cc.py" sessions "${CLAUDE_PROJECT_DIR}" <command>
| Intent | <command> |
|---|---|
| List sessions | (omit) |
| Delete a session | delete <uuid-prefix> |
| Prune old sessions | prune <duration> — e.g. 2w, 3d, 6m, 12h |
| Confirm prune | prune <duration> --confirm |
| Open the project folder | browse |
To delete by description ("the one about auth"), list first, pick the session,
then pass its UUID prefix (the xxxxxxxx shown) to delete.
Sessions marked ● are active and protected from deletion.
To manage other projects, or remove one entirely, use /projects.
npx claudepluginhub urav06/claudestrophobic --plugin claudestrophobicGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.