From session-tools
Detect and handle permission prompts in a Claude Code tmux session
How this skill is triggered — by the user, by Claude, or both
Slash command
/session-tools:approve-actionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Detect permission prompts and approve or deny them.
Detect permission prompts and approve or deny them.
$ARGUMENTS: <session-name> [approve|deny]
Parse arguments:
approve, deny, or none (interactive)Capture session output:
"$PLUGIN_DIR/bin/capture-session" "<session_name>" 30
Look for permission prompts:
Bash command: followed by commandAllow ... to ...Grant accessUse skill "..."If no permission prompt found:
No pending permission request in session '<session_name>'.
If permission prompt found, show details:
## Permission Request: <session_name>
**Type:** <Bash/Edit/Skill/etc>
**Details:** <what is being requested>
Options:
- approve: Allow this action
- deny: Reject this action
If action specified (approve/deny):
Send the appropriate response:
# For approve:
tmux send-keys -t "<session>" "y" && tmux send-keys -t "<session>" Enter
# For deny:
tmux send-keys -t "<session>" "n" && tmux send-keys -t "<session>" Enter
Report:
Sent '<action>' to session '<session_name>'.
Interactive:
/session-tools:approve-action ai-worker-001
## Permission Request: ai-worker-001
**Type:** Bash
**Details:** npm install express
Options:
- /session-tools:approve-action ai-worker-001 approve
- /session-tools:approve-action ai-worker-001 deny
Direct:
/session-tools:approve-action ai-worker-001 approve
Sent 'approve' to session 'ai-worker-001'.
npx claudepluginhub shsym/claude-session-tools --plugin session-toolsGuides 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.